Skip to main content
Glama

Visibility Genies

Get AI mentions gained and lost

get_ai_mention_changes

Buys the AI mentions a brand or domain gained and lost for this project, as Brand Lookup does: month by month over the last year, how many ChatGPT and Google AI Overview answers started mentioning it, how many stopped, and the net change, in mentions and AI search volume, in the United States. Estimated price: ~$0.92 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. 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_mention_changes"
  }
}

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

A3.9/5.0
Behavior3/5

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

Strong beyond the annotations: it discloses an estimated price (~$0.92), a hard per-call spend ceiling ($2.00 default from Settings), that funds are held to estimate-plus-margin while running, that only what was bought is charged, and that over-limit calls are refused before any purchase. Annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) already signal a non-destructive but externally-billing call, so this is real added context rather than the sole source. It doesn't say whether a partial/failed purchase is still billed, which is the remaining behavioral unknown for a paid tool.

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-loaded with purpose, then cost, then the refusal/approval path – the ordering matches the order an agent needs the information. Every sentence carries non-redundant content, but the opening clause ("Buys the AI mentions a brand or domain gained and lost") is grammatically tangled and the second half packs four billing rules into two long sentences, making it slower to parse than it needs to be.

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?

There is an output schema, so return values need not be described, and the description instead covers what the schema cannot: cost, caching, spend limits, refusal handling, and geographic/platform scope. For a billable, open-world tool with 4 well-documented parameters, an agent has everything needed to decide, call, and recover from a refusal.

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 meaning the schema cannot: approvedMaxCostUsd exists specifically because of the spend-limit refusal, must follow a user conversation, and must equal the amount the user approved. It also ties projectId to billing implicitly ("billed to" is in the schema, repeated here as the call being bought for the project). The scope parameter's exact_url/subfolder/domain semantics are left entirely to the schema, and 'as the page does' is the only extra hint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Buys the AI mentions a brand or domain gained and lost for this project" names a specific verb and resource, and the sentence continues with concrete scope: month-by-month over the last year, ChatGPT and Google AI Overviews, US only, gained/stopped/net. The only gap is sibling differentiation – it alludes to cached 'saved' reads and 'Brand Lookup' but never names get_ai_mentions_over_time or get_saved_ai_mentions_over_time as the non-billing alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear about the paid-vs-free split: what is saved and current for 24 hours is read free, and only a platform that is missing or out of date is bought, which tells an agent it is safe to call even when it does not know the cache state. It also gives an explicit recovery procedure for a refusal (ask the user, then retry with approvedMaxCostUsd). What it does not do is state when to prefer a different sibling tool instead of this one.

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