Quattr

page_traffic_cwv

Read-only

Which high-traffic organic pages have weak Core Web Vitals? Ranks a bounded top-N page set by Search Console clicks, fetches ONE selectable vital only for those exact pages — LCP seconds by default, or the 0–1 Lighthouse performance score, CLS, or INP via the vital parameter — and returns page, clicks, the vital value and grade, plus URL-match and freshness coverage. Use for page-level requests such as "top pages by organic clicks with LCP", "performance score for top 10 pages by clicks" (vital: "performance"), or "which high-traffic pages are slow". This is an observational page join, not causal correlation, and it is not an all-page export.

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": {
      "date_range": "<date_range>"
    },
    "name": "page_traffic_cwv"
  }
}

Input Schema

Name	Required	Description	Default
`top_n`	No	Number of pages selected by organic clicks before the CWV read (maximum 50).
`vital`	No	Which Core Web Vital to attach per page: lcp (default, seconds), performance (the 0–1 Lighthouse performance score — use for "performance score by pages"), cls (unitless), or inp (seconds).	lcp
`device`	No	Optional device applied identically to the organic-click and CWV legs.
`source`	No	Where Google search performance data is read from. Use "bigquery" ONLY when the user explicitly asks for BigQuery as the source AND describe_data_sources reports it available from live customer configuration — it returns far more granular per-query data (privacy-suppressed impressions appear under "[anonymized by google]").	default
`date_range`	Yes	Explicit date range, e.g. "2026-05-01 to 2026-05-31". Both endpoints are INCLUSIVE — the END day is covered (a 7-day range = 7 days). Quattr weeks run Sunday–Saturday; for "last week" use the most recent complete Sun–Sat span.
`page_filter`	No	Optional page scope applied to the GSC selection. CWV is then constrained to the exact selected URLs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it fetches exactly ONE vital per call, joins it only to the pre-selected click-ranked URLs, and returns freshness/URL-match coverage — all useful behavioral traits an agent could not get from annotations.

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?

Front-loaded with the guiding question, then the mechanism, then example triggers, then boundaries. It is dense but every clause carries meaning; only the dash-heavy inline enumeration of vitals is slightly more verbose than needed.

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?

With six parameters, a nested object, and no output schema, the description does well to explain the return shape (page, clicks, vital value and grade, URL-match and freshness coverage) and the source-selection caveat. It lacks only outward routing to alternative CWV tools for non-page-level needs.

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 description coverage is 100%, so every parameter (including the vital enum and source guidance) is already documented in the schema, making 3 the baseline. The description reinforces the vital meanings and the top-N click selection but adds little syntactic or format detail the schema lacks.

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 specific verb+resource chain: rank top-N pages by Search Console clicks, fetch one selectable vital for those exact pages, and return page/click/vital/grade. It distinguishes itself from siblings by explicitly labeling the operation as a page-level join and disclaiming all-page export and causal correlation.

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?

Gives concrete use cases ("top pages by organic clicks with LCP", "performance score for top 10 pages by clicks", "which high-traffic pages are slow") and explicit non-uses (not causal correlation, not all-page export). It does not name competing siblings like cwv_breakdown or site_health_cwv_check, leaving that routing to inference.

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

All Quattr 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?