Sign in
Docs
0%

Observe

Trails tools for assistants (MCP)

The 2 tools an assistant can call for Trails over MCP: what each one does, the scopes it needs, its arguments and an example call.

Recordings of how people moved through a site, made with their consent: pages, clicks, timings and errors, never what anyone typed. Failed requests from pages and the app are reported here too, grouped so the team can investigate each kind once. Use it to see what a person saw before something broke. An assistant calls these tools over MCP; the same operations over HTTP are in the Trails API. Tools for assistants lists every product, and MCP shows how to connect an assistant.

trails_list_error_groups

List error groups. The account's groups of similar failed requests from its pages and its app, most recent first: site, method, route template, status, how many, when, and the investigation once it has run. 0 means 50, at most 200.

Scopes: mcp:read, trail:read · reads only

ArgumentTypeWhat it is
page_sizeinteger0 means 50, at most 200.
page_tokenstringThe next_page_token of the page before.
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trails_list_error_groups",
    "arguments": {
      "page_size": 20
    }
  }
}

trails_get_error_group

Get an error group. One error group with its most recent reports (request ID, trace id, page route, never a value) and its investigation: the question, what is known, what is assumed, what can't be proven and what would settle it, each claim with its proof.

Scopes: mcp:read, trail:read · reads only

ArgumentTypeWhat it is
group_idstring
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trails_get_error_group",
    "arguments": {
      "group_id": "terr_01JD8Z3QK4W5X6Y7Z8A9B0C1D2"
    }
  }
}