get_auth_me_onboarding

Read-only

Calls GET /api/auth/me/onboarding as the signed-in person · REST reference

The first-time tours and popups the signed-in user has already seen

Answers about the caller only — there is no user to name. The state is stored on the caller's own account in the graph, so a tour dismissed on one device is dismissed on every device. An account that has marked nothing answers an empty list.

Arguments

This tool takes no arguments.

Example call

A client sends this over the MCP session; Claude and other agents build it for you. The values are placeholders — the shape is real.

json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_auth_me_onboarding",
    "arguments": {}
  }
}

Result

On success (HTTP 200) the tool returns one text item holding the API's JSON, pretty-printed.

The topics the caller has seen; an empty list when there are none.

json
{
  "data": {
    "seen": [
      "DASHBOARD_TOUR"
    ]
  },
  "success": true
}

Fields

FieldTypeDescription
dataobjectThe first-time tours and popups the signed-in user has already seen.
data.seenarray of "DASHBOARD_TOUR" | "PAYOUT_STEPS"In the order they were first seen. A topic appears at most once.
successtrue

When it fails

A failed call returns isError: true with the API's message as text.

What the model is shown

This is the tool exactly as the server lists it in tools/list. The description starts with the REST call it makes.

json
{
  "name": "get_auth_me_onboarding",
  "description": "GET /api/auth/me/onboarding — Answers about the caller only — there is no user to name. The state is stored on the caller's own account in the graph, so a tour dismissed on one device is dismissed on every device. An account that has marked nothing answers an empty list.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}