Skip to main content
Glama

Journey detail

journey_detail
Read-onlyIdempotent

Full observed history of one pseudonymous journey (visits, signups, payments) in time order, so you can say how a customer found the site. Take journey_id from the journeys tool. Paginate with cursor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "journey_id": "<journey_id>"
    },
    "name": "journey_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNopage size 1-100; default 50
cursorNonext_cursor from the previous page
journey_idYesjourney_id from the journeys tool (64 lowercase hex characters)
website_idNowebsite id (uuid) or the site domain (example.com); omit when the account has one website

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and an output schema exists, so the burden is low. The description usefully adds that results are time-ordered, that pagination is cursor-based, and that the data is pseudonymous with visits/signups/payments — but says nothing about how far back history goes, whether it is eventually truncated, or any result-size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler: what it returns first, then why it matters, then the two operational instructions. Front-loaded and every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple read-only tool with full schema coverage, rich annotations and an output schema — so return-shape detail is unnecessary. The remaining gap is temporal scope: 'full observed history' leaves unclear whether there is a retention window or maximum span an agent should expect across pages.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters (journey_id, limit, cursor, website_id) are already documented in the schema, including formats and defaults. The description only reinforces the journey_id provenance and cursor pagination, adding no meaning the schema lacks; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — the full observed history of ONE journey, containing visits, signups and payments in time order — plus the downstream question it answers ('how a customer found the site'). It is clearly distinguishable from the sibling 'journeys' tool, which is named as the source of the required id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the dependency chain explicitly ('Take journey_id from the journeys tool') and tells the agent to paginate with the cursor, which is how the tool is actually driven. It does not state when NOT to use it (e.g. do not call for aggregate counts — use journeys/insights instead), so it stops short of full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources