Skip to main content
Glama

Visibility Genies

Get web mentions

get_web_mentions

Finds web pages that name the project's brand (an exact phrase), for link building: each page's site, title, publish date, how it leans (positive, negative or neutral) and the site's 0 to 100 link-graph rank, strongest sites first and one page per site, with the project's own site left out. It cannot tell whether a page links to the project: a page is a prospect to check, and "site links to you" says yes only when the project's saved referring domains list the site. view "summary" instead returns how many pages name the brand, how they lean, and the 10 sites that name it most. Estimated price: up to $0.06 for pages (one request, billed by the up to 100 pages returned) or up to $0.05 for the summary. An answer saved within 7 days is read free; get_saved_web_mentions reads it without buying. save_link_prospect keeps a site as a prospect. 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": "get_web_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"pages": up to 100 pages that name the brand, one per site, strongest sites first. "summary": how many pages name it, how they lean, and the 10 sites that name it most.pages
brandNoThe brand name to look for, as an exact phrase. Defaults to the project's own brand name.
limitNoHow many pages to return. Defaults to 50.
offsetNoHow many pages to skip, to read further on.
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
viewNo
brandNo
savedNo
totalCountNo
savedResultIdNo

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 flag openWorldHint=true, readOnlyHint=false and destructiveHint=false; the description goes well beyond by pricing each view (up to $0.06 / $0.05), explaining that a result saved within 7 days is read free, describing the spend-limit hold-and-charge behavior, and spelling out the refusal flow with approvedMaxCostUsd. It also discloses a real capability limit (it cannot tell whether a page links to the project) and defines when "site links to you" is true, which prevents a costly misinterpretation.

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 core purpose and the pages-vs-summary distinction are front-loaded, and nearly every sentence carries operational weight (cost, cache, refusal, exclusions). It is, however, a single dense run-on block with pricing and spend-limit policy interleaved with result semantics, which makes it harder to scan 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?

For a paid, open-world tool with six parameters, the definition covers cost, caching, spend-limit refusal, result shape, ordering, deduplication (one page per site), and a key limitation, so an agent can decide and call without guessing. An output schema exists, so restating return fields is a bonus rather than a necessity.

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 schema already defines view, brand, limit, offset and projectId; the description nonetheless adds the billing coupling (pages billed by up to 100 returned), the exact-phrase matching rule for brand, and the fact that offset exists to page further into results. approvedMaxCostUsd gets real semantics only in the description, including the warning never to set it without asking the user.

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 ("finds web pages that name the project's brand") plus the exact match rule, and immediately characterizes the output fields and ordering. It distinguishes itself from the saved-answer sibling (get_saved_web_mentions) and from save_link_prospect, and it explicitly names the alternate "summary" view rather than hiding it behind the schema enum.

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 routing rules: use view "summary" when you want counts and top-10 sites instead of pages, use get_saved_web_mentions when a free saved answer exists, and use save_link_prospect to retain a site. It also states the negative condition (own site excluded) and the escalation path when a call is refused for cost, so the agent knows what to do next rather than just what the tool does.

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