Skip to main content
Glama

Visibility Genies

Read saved web mentions

get_saved_web_mentions
Read-only

Reads the web pages that name the project's brand, or their summary (view "summary"), as saved by Link Prospects' Mentions tab, Perception's "On the web" or get_web_mentions, however old, for free. It never buys: when nothing is saved it names the price get_web_mentions would pay.

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_saved_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.

Output Schema

NameRequiredDescriptionDefault
metaNo
rowsNo
viewNo
brandNo
savedNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, but the description adds information they cannot carry: this call never incurs purchase cost, and it returns stale data ("however old") with a price quote as the empty-result behavior. Freshness and cost are exactly the traits an agent needs before choosing between it and the buying sibling.

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?

Two sentences, front-loaded with the core action and the cost guarantee, with no filler. It is slightly dense with product-surface references ("Link Prospects' Mentions tab, Perception's 'On the web'") that slow parsing without adding agent-relevant meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema handling return shape, full schema descriptions, and annotations covering safety, the description supplies the remaining gaps: provenance of the saved data, staleness tolerance, and cost behavior. Only explicit pagination guidance (using offset to read further) is left entirely to the schema.

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 schema already explains view, brand, limit, offset and projectId in detail. The description's mention of the "summary" view and brand naming only restates what the enum and property descriptions provide, so the baseline 3 applies.

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 uses a specific verb ("Reads") plus a precisely scoped resource ("the web pages that name the project's brand") and explicitly contrasts itself with get_web_mentions, which buys fresh data. An agent can distinguish it from the sibling 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?

It establishes the cached/free path versus the paid get_web_mentions path and tells the agent what happens when nothing is saved (the price get_web_mentions would pay), which is effectively conditional routing. It stops short of saying when to abandon the saved data and pay for a fresh pull.

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