Quattr

ai_visibility_overview

Read-only

AI answer-engine (ChatGPT/Perplexity/Gemini/AI Mode) citations — NOT Google's on-SERP AI Overviews (use competitive_trends/competitive_overview for those). The CURRENT AI-visibility Home grid for one tracker: citation rate, share of voice, mentions and positive sentiment per configured AI answer platform, plus the selected tracker's cross-platform aggregate. Use for "how visible are we across AI answer engines?" / "our AI answer scorecard". If tracker is omitted, one tracker is auto-selected; multiple trackers return a picker without querying. Supports comparison_range and tracker-scoped country/device filters. For one metric OVER TIME use ai_visibility_trend; for the per-competitor breakdown use ai_visibility_competitors.

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": "ai_visibility_overview"
  }
}

Input Schema

Name	Required	Description
`brand`	No	Restrict to BRANDED ("Yes") or NON-BRANDED ("No") prompts — branded prompts (e.g. "example-brand login") behave very differently from category prompts (e.g. "best web hosting"); a blended number mixes them. Omit for all prompts.
`device`	No	Optional device filter. Values are normalized to uppercase, e.g. DESKTOP or MOBILE. Applied on the same tracker-scoped AI visibility reads as country. Overview and citation audit require a tracker. If the underlying data has no device filter, the tool says so and returns no totals.
`intent`	No	Restrict to one search intent, e.g. "Informational" / "Transactional".
`country`	No	Optional country filter, e.g. "USA". Applied on tracker-scoped AI visibility reads (overview, citation audit, competitors, trend, and drilldown). Overview and citation audit require a tracker. The geography drilldown tab groups rows by country instead of filtering them. If the underlying data has no country filter, the tool says so and returns no totals.
`tracker`	No	AI Visibility tracker (unified segment id), e.g. "AI Tracker". If omitted, the only ACTIVE tracker is auto-selected; multiple trackers (or only paused ones) return a picker without querying. A paused tracker (collection stopped on its end date) is honored when named explicitly, and the result carries trackerStatus "paused" — report it as historical, not current.
`platform`	No	Restrict to one AI platform, e.g. "chatgpt" / "gemini" (platform key).
`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.
`comparison_range`	No	Explicit comparison range for period-over-period, e.g. "2026-04-01 to 2026-04-30". Adds per-row deltas (delta + deltaPct) for the metrics; never changes which rows return (deltas are left-joined onto the selected period).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 20, 2026

changedInput schema / properties / country / description

Previous value: -"Optional QWA country filter, e.g. \"USA\". For ai_visibility_overview this requires a tracker and reads QWA drilldown-backed client metrics; for ai_visibility_drilldown, the geography tab groups rows by country."New value: +"Optional country filter, e.g. \"USA\". Applied on tracker-scoped AI visibility reads (overview, citation audit, competitors, trend, and drilldown). Overview and citation audit require a tracker. The geography drilldown tab groups rows by country instead of filtering them. If the underlying data has no country filter, the tool says so and returns no totals."

changedInput schema / properties / device / description

Previous value: -"Optional QWA device filter. Values are normalized to QWA uppercase, e.g. DESKTOP or MOBILE. For ai_visibility_overview this requires a tracker."New value: +"Optional device filter. Values are normalized to uppercase, e.g. DESKTOP or MOBILE. Applied on the same tracker-scoped AI visibility reads as country. Overview and citation audit require a tracker. If the underlying data has no device filter, the tool says so and returns no totals."

changedInput schema / properties / tracker / description

Previous value: -"AI Visibility tracker (unified segment id). If omitted, the only tracker is auto-selected; multiple trackers return a picker without querying."New value: +"AI Visibility tracker (unified segment id), e.g. \"AI Tracker\". If omitted, the only ACTIVE tracker is auto-selected; multiple trackers (or only paused ones) return a picker without querying. A paused tracker (collection stopped on its end date) is honored when named explicitly, and the result carries trackerStatus \"paused\" — report it as historical, not current."

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds real behavioral context on top: multi-tracker requests return a picker without querying, an explicitly named paused tracker is honored and flagged with trackerStatus "paused" (report as historical), and missing device/country data yields an explicit message with no totals. This is well beyond what the annotations disclose.

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?

Dense and front-loaded: identity and the AI-Overviews exclusion come first, then return content, then the two sibling routes. It is one long block with several parentheticals, which is heavier than ideal, but no sentence is filler.

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 an 8-parameter read-only tool with no output schema, the description covers what the result contains (per-platform metrics plus tracker aggregate), the fallback behaviors (auto-select/picker/paused), and the filter scope. Nothing an agent needs to select or invoke it correctly is missing.

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 the schema already documents tracker auto-selection, date_range inclusivity, and comparison_range delta/left-join behavior. The description reinforces that comparison_range and tracker-scoped country/device filters are supported but adds no syntax or semantics the schema lacks, so the 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?

States a specific resource (the CURRENT AI-visibility Home grid for one tracker) with named metrics (citation rate, share of voice, mentions, positive sentiment) and a cross-platform aggregate, and explicitly disambiguates from Google's on-SERP AI Overviews by naming the siblings to use instead. An agent can distinguish it from ai_visibility_trend and ai_visibility_competitors without opening any schema.

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?

Provides explicit when-to-use phrasing ("how visible are we across AI answer engines?" / "our AI answer scorecard"), an explicit when-not-then-what (on-SERP AI Overviews → competitive_trends/competitive_overview), and routes the two adjacent use cases to ai_visibility_trend (over time) and ai_visibility_competitors (per-competitor). The tracker-omission path is also spelled out (auto-select; picker without querying).

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?