Skip to content
HeyCrustDocs

Search documentation

Search by topic or tool name
Partner portalOpen app ↗
Browse documentation
Tool reference

get_setup_guide

Returns app identity, observations/sources, app-specific pixel/identify/backfill/uninstall snippets, custom event examples and the setup instructions.

Verified ·Read Markdown
On this page

Purpose

Everything needed to wire ONE app's codebase to Crust: ready-to-paste snippets (pixel, identify-on-install hook, one-time backfill route, no-token webhook alternative) with real ids baked in, plus step-by-step agent instructions and current status. Call after list_apps when integrating an app; apply the snippets to the repo you're working in.

Credentials and scope

Owner workspace credential. The credential determines tool visibility. For tools with appId, use the HeyCrust app UUID from list_apps; the dashboard app selector does not supply MCP arguments for you.

Inputs

  • appId: required; string; format: uuid — The app id from list_apps.

Example request

The identifiers and merchant are fictional. Replace them with records returned for your own workspace; this example is schema-checked, not a promise that the fictional record exists.

json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_setup_guide",
    "arguments": {
      "appId": "11111111-1111-4111-8111-111111111111"
    }
  }
}

POST this JSON to https://heycrust.com/api/mcp with Content-Type: application/json and Authorization: Bearer <YOUR_CREDENTIAL>. The tool result normally contains JSON encoded as text in result.content; inspect JSON-RPC errors and result.isError before using it.

Result

Returns app identity, observations/sources, app-specific pixel/identify/backfill/uninstall snippets, custom event examples and the setup instructions. Select the correct framework and follow its consent/verification steps.

Effects and verification

Reads existing records or definitions. It does not create a payment or send a message. Verify the returned app/merchant identity and source coverage before interpreting the result.

Troubleshooting

A missing tool can mean that the credential lacks its catalog or required scopes. Invalid arguments are different from unavailable source data or a record outside the workspace. A handler can return a business error even when the argument schema is valid. Read MCP overview and Help.

Continue reading