Conecto

Check how fast pages are for real visitors

analytics_web_vitals

Read-onlyIdempotent

Core Web Vitals measured in visitors' browsers: LCP, INP, CLS, FCP and TTFB at the 75th percentile, rated good, needs_improvement or poor the way Google does, overall and by device, and the pages with the slowest LCP. 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_web_vitals"
  }
}

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral value: field data rather than synthetic, 75th-percentile aggregation, Google rating thresholds, and that results include a slowest-LCP page list. It does not say how that page list is bounded (the limit param) or how period defaults affect results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loaded with the resource and expanded into metrics, rating scheme, breakdowns, and the slow-LCP list; the trailing 'Free.' is short and informative. Slightly list-heavy but no sentence is wasted.

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?

Eight parameters, a nested filters object, and no output schema make this a moderately complex tool. The description conveys the broad shape of results (overall, by device, slowest pages), but leaves the period/date-window behavior, limit semantics, and filter narrowing entirely to the schema.

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 only 50%, so the description should compensate more. It does map to the 'device' breakdown and implies a page-level list (limit), but says nothing about site, period/from/to, page, or the filters object, all of which the agent must read from the schema alone.

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?

States the exact resource (Core Web Vitals: LCP, INP, CLS, FCP, TTFB) measured from real visitor field data and the aggregation (75th percentile, Google rating bands). This clearly separates it from analytics_stats/analytics_breakdown by content, though no sibling is named explicitly.

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?

The 'in visitors' browsers' and 'Free.' phrasing implies when it is appropriate (performance auditing at no cost) versus other analytics tools, but there is no explicit when-to-use/when-not statement or named alternative such as analytics_stats or analytics_problems.

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?