Skip to main content
Glama

Quattr

ai_visibility_citation_audit

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). CURRENT citation counts and rate (point-in-time) for one AI Visibility tracker: selected-tracker citation rate plus its per-platform citation counts for a date range. Use for "are our citations dropping?" / "how often are we cited on AI platforms?". If tracker is omitted, one tracker is auto-selected; multiple trackers return a picker without querying. country and device filters are applied when a tracker is in scope; they are not silently ignored. For citations OVER TIME as a trend, use ai_visibility_trend instead.

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_citation_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoRestrict 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.
deviceNoOptional 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.
intentNoRestrict to one search intent, e.g. "Informational" / "Transactional".
countryNoOptional 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.
trackerNoAI 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.
platformNoRestrict to one AI platform, e.g. "chatgpt" / "gemini" (platform key).
date_rangeYesExplicit 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_rangeNoExplicit 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.

  1. Changed3 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / device
      Added value: +{
      +  "description": "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.",
      +  "type": "string"
      +}
    • 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."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare the safe read-only profile, and the description adds substantial context beyond them: tracker auto-selection, the multiple-tracker picker that returns without querying, paused-tracker handling reported as historical, and the explicit promise that country/device are not silently ignored. This is exactly the behavioral disclosure that structured fields cannot carry.

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 but front-loaded and logically ordered: scope distinction, what it returns, usage triggers, tracker/filter behavior, then the trend alternative. Nearly every sentence earns its place, though the parenthetical alternates make it slightly heavy.

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?

With no output schema, the description still conveys the return shape (selected-tracker citation rate plus per-platform counts), the auto-selection and picker behaviors, and the paused-tracker caveat. Combined with 100% schema coverage, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds interpretation beyond the schema: branded vs non-branded prompts behave differently and blending them is misleading, filters only apply when a tracker is in scope, and date_range endpoints are inclusive. It enriches parameter understanding rather than merely restating fields.

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 (citation counts and rate for one AI Visibility tracker) and explicitly bounds scope against two alternatives: Google's on-SERP AI Overviews and the ai_visibility_trend sibling. An agent can distinguish this from every related sibling without opening a 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?

Gives explicit when-to-use triggers ("are our citations dropping?" / "how often are we cited"), names the wrong-tool cases with the correct alternatives (competitive_trends/competitive_overview for Google AI Overviews; ai_visibility_trend for over-time trends), and states the point-in-time nature. Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources