Conecto

See where people go

analytics_paths

Read-onlyIdempotent

With a page: where visits went next (or left the site) and where they were before it. Without one: the commonest journeys, the first four pages of visits. Free.

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": {
      "site": "<site>"
    },
    "name": "analytics_paths"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	With period custom: the last day.
`from`	No	With period custom: the first day, 2026-10-01.
`page`	No	Like /pricing; * for any part.
`site`	Yes	The site's domain (e.g. halversoncycle.example) or its site_id.
`limit`	No
`period`	No		30d
`filters`	No	Narrow the stats: page and entry_page ("/blog/", for any part), goal (a goal's name), event, channel (Direct, Organic search, Paid search, Organic social, Paid social, AI assistants, Email, Referral, Affiliates, Display, Paid other, Other campaigns), source ("Google", "Direct"), referrer, campaign, medium, term, content, country ("DE"), device (desktop, tablet, mobile), browser, os. Example: {"channel": "Organic search", "device": "mobile"}.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the bar is lower; the description still adds real context: the conditional output shape, that the page-less mode returns only the first four pages of journeys, and 'Free' signalling no quota cost. It does not mention result limits (limit max 50) or how period interacts with the two modes.

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?

Two short sentences, the two-mode behavior front-loaded and the cost note trailing with no wasted words.

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

Completeness3/5

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

For a 7-parameter analytics tool with a nested filters object and no output schema, the description covers the core behavioral fork and cost but leaves the filter vocabulary, limit semantics, and default period to the schema. Adequate but not complete.

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?

At 71% schema coverage the schema documents site, page, from/to, period, and the nested filters object. The description adds meaning only for page ('with a page' / 'without one'), plus a hint that the page-less result is truncated to four journey pages. It says nothing about the limit, period default, or filters semantics beyond the schema.

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 states the specific report: next/previous page journeys, and the aggregated commonest journeys when no page is given. That distinguishes it from a generic breakdown tool, though it never names the sibling (analytics_breakdown, analytics_funnel) it is not.

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?

It explains the two operating modes keyed to the page parameter, which is genuine usage guidance for that one parameter. It gives no indication of when to prefer this over analytics_funnel, analytics_breakdown, or analytics_stats, and no prerequisites for site/period setup.

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

All Conecto tools Inspect

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

Need Help?