Skip to main content
Glama

Quattr

ai_visibility_trend

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). Use ONLY for OVER-TIME / trend questions (a time series). Citations, share of voice and positive sentiment bucketed by day/week/month/quarter for one tracker, optionally for a single AI platform or search intent. Use for "is our AI visibility going up or down?" / "AI citations over the last 3 months". If tracker is omitted, one tracker is auto-selected; multiple trackers return a picker without querying metrics. For the current snapshot use ai_visibility_citation_audit; for 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_trend"
  }
}

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".
metricNoDISPLAY-ONLY card metric (does not change the query): cit=citations (default), sov=share of voice, men=mentions, sen=sentiment.
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).
chart_viewNoCard perspective: "platforms" (default, per-platform lines) or "allmetrics" (all four metrics, indexed) are display-only over the same per-platform series; "competitors" CHANGES the query — it returns a per-competitor over-time series (competitorSeries) from competitor_details (C6).
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.
value_modeNoDISPLAY-ONLY card value mode (does not change the query): "pct" (default, percentage) or "total" (raw count).
granularityNoTrend bucket size: day, week (default), month or quarter.
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
    • 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."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.3/5.0
Behavior4/5

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

Annotations already cover readOnlyHint/destructiveHint/openWorldHint, so the safety profile is settled. The description adds genuine behavior: tracker auto-selection, a picker returned without querying metrics when multiple trackers exist, and paused-tracker handling reported as historical. However, most of these behaviors are also spelled out in the tracker/chart_view schema fields, so its unique contribution beyond structured data is moderate.

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-loads the most important disambiguation (the NOT-Google boundary) and then routes to siblings. Dense but each sentence carries routing or scoping value; slightly long, though no clearly wasted sentences.

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 no output schema, the description does describe returned content (citations, share of voice, positive sentiment bucketed by period, competitorSeries for the competitors view) and the picker/no-query edge case. Sufficient for correct invocation, though return-shape detail is high-level.

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 all 12 parameters in detail. The description restates the metric/platform/intent/bucketing options rather than adding syntax or format detail the schema lacks, landing at the baseline when structured fields do the heavy lifting.

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+scope: AI answer-engine citations as an over-time time series, bucketed by day/week/month/quarter. It explicitly draws the boundary against Google AI Overviews and against the snapshot/competitor siblings, so an agent can distinguish it 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?

Gives explicit when-to-use ('ONLY for OVER-TIME / trend questions'), when-not-to-use (NOT Google AI Overviews; not the current snapshot; not per-competitor), and names the correct alternative tools (competitive_trends, ai_visibility_citation_audit, ai_visibility_competitors). Routing is unambiguous.

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