Skip to main content
Glama
Sign In

twelvebit Analytics

by app.twelvebit
OverviewDiscussionsAdmin

One visitor's journey

get_journey
Read-onlyIdempotent

Everything about one visitor: profile, first touch, the visit credited with their first payment, every visit with its pages and goals, and payments. Each pageview event includes scroll_depth_percent (0–100, maximum content exposure for that view; null when unavailable). Repeated views retain their own depth; this does not measure reading. Pass a visitor_id from list_people or get_realtime, or your own user id.

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_id": "<visitor_id>"
    },
    "name": "get_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite domain (example.com), id or public id (tb_…). Optional with a site key, or when the account has one site.
visitor_idYesVisitor id or user id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context not in the annotations: the meaning and edge cases of scroll_depth_percent (0-100, null when unavailable, per-view rather than per-visitor, and explicitly not a reading measure). Return-shape disclosure matters here because no output schema exists.

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?

Front-loads the payload contents in one sentence, then follows with the single non-obvious output caveat (scroll depth) and the id-sourcing note. The parenthetical is long but every clause carries disambiguating information; nothing is padding.

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?

For a two-parameter read tool with no output schema, the description adequately conveys what comes back and gives the one semantic trap warning. Missing only hints about response size or pagination for visitors with very long journeys, which is a minor gap.

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

Parameters4/5

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

Schema coverage is 100%, which sets a baseline of 3, and the description goes beyond it by specifying where visitor_id comes from (list_people, get_realtime, or your own user id). The optional 'site' parameter is left to the schema, which documents it adequately.

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 concrete verb/resource pair ('Everything about one visitor') and then enumerates exactly what is returned: profile, first touch, credited visit, all visits with pages and goals, and payments. This is clearly distinguishable from list_people (enumeration) and get_realtime (live view), both of which are named.

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?

Explicitly tells the agent how to obtain the required input by naming the sibling tools list_people and get_realtime as sources for visitor_id, and allows a user id as an alternative. It stops short of stating when not to use this tool (e.g., bulk lookup vs single visitor), so no explicit exclusion is present.

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

All twelvebit Analytics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources