Staats

Journeys

journeys

Read-only

The routes visitors actually take, grouped into identical sequences and counted, busiest first. Use this when you do NOT already know the steps: funnel measures a path you name, journeys discovers the ones you did not think to check. A step is a pageview path (/pricing) or a custom event marked with a leading # (#signup_click), so the moment of conversion appears in the route. Consecutive repeats are collapsed and only the first 10 steps define a route. contains filters to routes that include a given path or event: run it once with and once without to see what converting visitors do differently. Visitor identity rotates daily, so a route is one day of activity and describes a group, never a person.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	ISO end, alternative to period
`from`	No	ISO start, alternative to period
`site`	No	the site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
`limit`	No	max routes returned (default 20)
`period`	No	relative period like '24h', '7d' (default), '4w'
`contains`	No	only routes that include this path or #event step

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`site`	Yes
`period`	Yes
`contains`	No
`journeys`	Yes
`total_visitors`	Yes

TDQS

A4.9/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the readOnlyHint annotation: consecutive repeats are collapsed, only the first 10 steps define a route, and visitor identity rotates daily so a route describes a group rather than a person. This gives the agent critical expectations about grouping semantics and privacy boundaries that the schema and annotations do not convey.

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?

The description is dense but every sentence earns its place: purpose, sibling differentiation, step syntax, deduplication/truncation rules, contains behavior, and identity rotation are all covered without filler. It is front-loaded with the main purpose before moving into usage and edge-case semantics.

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

Completeness5/5

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

For a complex analytics tool with 6 optional parameters and an output schema, the description covers the conceptual model, route grouping rules, the conversion-event representation, contains-filter workflow, and the daily identity limitation. Combined with the readOnly annotation and schema coverage, nothing critical is missing for an agent to select and invoke this tool correctly.

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?

The schema already documents all 6 parameters with 100% coverage, so the baseline is 3. The description adds meaningful semantics beyond that by explaining the step format for path vs #event and by clarifying what the contains parameter actually does at the route level, which helps the agent construct correct parameter values.

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?

The description opens with a clear verb-resource pairing: "routes visitors actually take, grouped into identical sequences and counted, busiest first." It explicitly distinguishes journeys from funnel by naming what each does, so an agent can tell them apart without inspecting schemas.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use rule: "Use this when you do NOT already know the steps: funnel measures a path you name, journeys discovers the ones you did not think to check." It also advises how to use the contains filter by running the tool once with and once without it, which is actionable usage guidance.

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

All Staats tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool maps to a distinct resource or action: site management, site context, annotations, overviews, dimensional queries, funnels, journeys, and anomaly checks. Overlapping pairs like funnel/journeys are explicitly disambiguated in the descriptions, and what_broke vs what_changed cleanly separate problems from notable movements.

Naming Consistency3/5

Most tools follow a clear verb_noun pattern such as create_site, list_annotations, and update_site_context, but funnel, journeys, portfolio_overview, what_broke, and what_changed break that pattern. The names are still readable and somewhat grouped by intent, but the mixed conventions make it harder to predict a tool's role from its name alone.

Tool Count5/5

At 15 tools this sits at the upper edge of the ideal range, and each tool earns its place: site lifecycle, context, annotation timeline, core analytics, discovery reports, and post-deploy checks are all covered. There is no obvious redundancy or filler.

Completeness4/5

The set covers site management, context editing, annotations, overview/query/funnel/journeys/portfolio analytics, and what_broke/what_changed checks, so most workflows have no dead ends. Minor gaps exist, such as no way to edit or delete a mistaken annotation and no explicit tool for updating data-retention settings, but these are workaroundable rather than blocking.

Resources

Need Help?