Skip to main content
Glama

Visibility Genies

Read saved AI mentions over time

get_saved_ai_mentions_over_time
Read-only

Reads the AI mentions over time already bought for a brand or domain in this project: its mentions and AI search volume in ChatGPT and Google's AI Overviews, month by month, in the United States. Uses no credits and never buys: a platform that is not saved or out of date is named with the price Brand Lookup's refresh asks for it, and get_ai_mentions_over_time buys it at that price, as the page does.

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": {
      "projectId": "<projectId>",
      "query": "<query>"
    },
    "name": "get_saved_ai_mentions_over_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe brand or domain, as it was looked up on the Brand Lookup page.
scopeNoFor a domain: the scope it was looked up with. Omit to derive it from the query, as the page does.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
toBuyYes
platformsYes
toBuyPriceUsdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly and non-destructive annotations, it discloses that no credits are used, no purchase occurs, and missing or out-of-date platforms are named with the price Brand Lookup's refresh asks for. That is exactly the behavioral context an agent needs before choosing between reading saved data and buying fresh data.

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?

The description is front-loaded with purpose and scope, then adds the key behavioral distinction from the buying sibling. The second sentence is somewhat long and carries multiple clauses, but each clause conveys useful purchasing or data-availability behavior.

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?

The tool has an output schema, so the description need not explain return values, and the annotations already cover safety. Given that, the description supplies enough context about saved versus fresh data, geography, platforms, and billing-adjacent behavior for an agent to call it correctly.

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 query, scope, and projectId parameters are already well documented in the schema. The description reinforces that the query is a brand or domain and that data is scoped to the project, but it does not add syntax or format detail beyond the schema.

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?

The description states a specific verb and resource: it reads saved AI mentions over time for a brand or domain, including mentions and AI search volume in ChatGPT and Google's AI Overviews month by month in the US. It also distinguishes this saved-data tool from the buying sibling get_ai_mentions_over_time.

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?

It explicitly says the tool uses no credits and never buys, and names get_ai_mentions_over_time as the alternative that purchases missing or out-of-date data at the stated price. That gives clear when-to-use and when-to-use-the-other-tool guidance.

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