Conecto

Show someone the stats

analytics_view_link

A one-time link to a page with the site's stats for a person to look at: visitors and how they changed, a chart by day, channels, pages (each with its heatmap), sources, countries, devices, goals and speed. The first browser that opens it keeps it for an hour; an unopened link expires after 7 days. Conecto keeps no dashboard: make a link whenever someone should see the numbers (view_show draws anything else). 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_view_link"
  }
}

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.
`site`	Yes	The site's domain (e.g. halversoncycle.example) or its site_id.
`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

A4.4/5.0

Behavior4/5

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

Annotations already flag this as a non-read-only, non-idempotent create, and the description adds genuinely new lifecycle detail: the first browser keeps the link for an hour, unopened links expire after 7 days, and it is free. It does not cover permissions/auth or whether an existing link is invalidated, which keeps it short of a 5.

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-loaded with the core purpose, then scope of the page, then expiry behavior, then the routing rule. The long content enumeration is dense but each item tells the agent what it can expect the link to display.

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?

No output schema exists, and the description makes it clear a link (i.e., a URL) is produced plus its lifetime, which is sufficient. Minor gap: it never states the response shape or whether the link appears in a field, leaving a small inference.

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 coverage is 80%, so period/from/to/filters are already documented in the schema. The description's list of page contents (channels, pages, countries, devices) loosely hints at what filters narrow, but it adds no explicit parameter guidance beyond that; 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?

Opens with a specific verb and artifact: 'A one-time link to a page with the site's stats.' It enumerates exactly what the page contains and explicitly contrasts itself with view_show, so an agent can tell the two apart without reading 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?

'Conecto keeps no dashboard: make a link whenever someone should see the numbers (view_show draws anything else)' gives both the trigger condition and the named alternative with its exclusion. Nothing is left to inference about when to pick this tool.

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?