Skip to main content
Glama

Tally by Outpost

Visitor journey

get_visitor
Read-onlyIdempotent

One visitor's whole journey: every visit with its pages, engaged time, goals and outbound clicks, their payments, first touch and the touch credited with the sale.

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": {
      "visitor": "<visitor>"
    },
    "name": "get_visitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoThe site's id. Optional: the API key's site is the one read.
cursorNoThe next_cursor of the previous page, to read on.
visitorYesA visitor's key from list_visitors (a visit's session id on a cookieless site).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context by listing exactly what the journey includes — pages, engaged time, goals, outbound clicks, payments, and both first-touch and sale-credited touch — which tells the agent what data will be returned. It does not mention pagination behavior despite the cursor parameter.

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?

A single front-loaded sentence with no redundant wording; the key object ('One visitor's whole journey') leads and the supporting enumeration follows compactly.

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?

With no output schema, the description usefully enumerates the returned journey components, which is the main completeness need. The only notable gap is cursor/pagination behavior, but annotations and the schema cover the safety and parameter side adequately.

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 the schema already explains site, cursor, and visitor semantics, including that visitor is a key from list_visitors. The description adds no further parameter meaning, which is acceptable at full coverage but earns only the baseline.

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

Purpose4/5

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

The description names the specific resource — one visitor's whole journey — and enumerates the contents (visits, pages, engaged time, goals, outbound clicks, payments, touch attribution). It clearly separates this from aggregate tools like get_breakdown or get_overview, though it does not explicitly name a sibling alternative.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'One visitor's whole journey,' suggesting this is for deep per-visitor inspection rather than aggregate reporting. However, it never states when to choose this over list_visitors or get_purchase_paths, nor does it explain how to obtain the visitor key beyond what the schema already says.

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