Skip to main content
Glama

Visibility Genies

Find sites AI answers cite

find_ai_cited_sites

Finds the 50 sites ChatGPT's answers about a topic cite as sources most (United States, English), as link prospects: keep one with save_link_prospect. Estimated price: up to $0.30, billed by the rows returned. An answer saved for the topic within a day is read free. 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>"
    },
    "name": "find_ai_cited_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoA topic or keyword, e.g. 'crm software'. Defaults to the project's last Brand Performance topic.
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
rowsNo
boughtNo
savedResultIdNo

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?

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=true; the description goes far beyond by disclosing per-row billing up to $0.30, a free read when a topic's answer was saved within a day, the workspace agent spend limit ($2.00 default, Settings-changeable), the hold-at-estimate-plus-margin mechanic, and that a refused call buys nothing. This is exactly the cost and side-effect context an agent needs before spending money.

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 what the tool returns and the scope before any billing detail, which is the right order. The billing/limit sentence is long and clause-heavy ('it holds at most its estimate plus a margin while it runs and is charged what it bought, never more'), but each sentence carries information an agent needs to avoid a failed or overspending call.

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?

Return shape is covered by an output schema, so the description is free to spend its words on cost, limits, and the save_link_prospect handoff, which it does. For a paid, open-world tool with only three parameters, nothing material about calling it correctly 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; the description earns above that by explaining the operational trigger and constraints for approvedMaxCostUsd ('only after a call was refused... ask the user, then call again') rather than just restating it. It also flags the topic default indirectly through scope, though the schema itself carries that detail.

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?

Opens with a specific verb and a precisely scoped resource: the 50 sites cited most by ChatGPT answers for a topic, restricted to United States and English, and framed as link prospects. That scope alone separates it from find_link_competitors and find_sites_using_technology 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 Guidelines4/5

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

Gives a clear follow-on path ('keep one with save_link_prospect') and a concrete recovery procedure when a call is refused for exceeding the workspace spend limit: ask the user, then retry with approvedMaxCostUsd. It never explicitly states when to prefer find_link_competitors or find_sites_using_technology over this tool, so alternatives are left implicit.

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