Skip to main content
Glama

Visibility Genies

Get AI mentions over time

get_ai_mentions_over_time

Buys the AI mentions over time of a brand or domain for this project, as Brand Lookup does: its mentions and AI search volume in ChatGPT and Google's AI Overviews, month by month, in the United States. Estimated price: ~$0.44 for both platforms. What is saved and current (for 24 hours), here or on the page, is read free, and only a platform missing or out of date is bought. It opens free on Brand Lookup; get_saved_ai_mentions_over_time reads it without buying. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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

Input Schema

NameRequiredDescriptionDefault
queryYesThe brand or domain, e.g. 'example.com' or 'Example Brand'.
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.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
boughtYes
platformsYes
savedResultIdNo
accountRefusalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description goes far beyond by disclosing the ~$0.44 estimate, the workspace agent spend limit ($2.00 default), the hold-plus-margin behavior, that charges never exceed what was bought, and that over-limit calls are refused before any purchase. This is exactly the cost/side-effect context an agent needs for a paid call.

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?

Purpose and cost are front-loaded and every sentence carries operational information. The middle sentence about what is saved and current is somewhat convoluted and could be tightened, but there is no 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 a paid, open-world read with an output schema already covering return values, the description supplies everything else an agent needs: cost, spend-limit enforcement, refusal handling, caching window, and the free alternative. Nothing material is missing.

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 the baseline is 3, but the description adds real meaning: it explains the purpose and safe-use protocol of approvedMaxCostUsd (only after a refusal, only with user approval) and clarifies that scope is derived from the query when omitted. It does not add format detail for query or scope 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?

States a specific verb and resource ('Buys the AI mentions over time of a brand or domain') plus the data returned (mentions and AI search volume in ChatGPT and Google AI Overviews, monthly, US). It also explicitly distinguishes itself from the sibling get_saved_ai_mentions_over_time, so an agent can route correctly without opening either 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 rules: saved/current data (24h) is read free here or on the page, only a missing or out-of-date platform is bought, and get_saved_ai_mentions_over_time reads without buying. It also names the refusal condition and the recovery path (ask the user, retry with approvedMaxCostUsd).

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