Skip to main content
Glama

Visibility Genies

Read saved brand mentions

get_saved_brand_mentions
Read-only

Reads Brand Mentions already bought for a brand in this project, however old, for free: the web pages that mention it, their tone, the sites that mention it most and mentions by month. It never buys: what is missing or out of date is named with the price get_brand_mentions would pay for it.

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

Input Schema

NameRequiredDescriptionDefault
brandNoThe brand name to look for. Omit for the project's own, as saved in its context.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
excludeDomainNoA site whose own pages are left out. Defaults to the project's domain.

Output Schema

NameRequiredDescriptionDefault
metaNo
savedNo
keywordNo
summaryNo
mentionsNo
excludeDomainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/non-destructive, and the description adds real behavioral context beyond them: no charge is incurred, arbitrarily old data is acceptable, and gaps are reported with the price a purchase would cost. That cost/no-purchase disclosure is the key behavior an agent needs before calling a billing-adjacent 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?

Two sentences, front-loaded with the read-only, no-charge guarantee, with zero filler. The middle clause ('the web pages that mention it, their tone, ...') is a slightly run-on enumeration, but it is informative rather than padding.

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 present, the description need not explain return shape, and it correctly spends its words on the cost model, staleness tolerance, and the hand-off to get_brand_mentions. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so brand, projectId, and excludeDomain are already fully documented, including defaults. The description adds only the billing/ownership framing ('for a brand in this project') rather than new meaning for any individual parameter.

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 ('Reads Brand Mentions already bought for a brand in this project') and immediately contrasts with the purchasing sibling get_brand_mentions. An agent can tell this apart from get_brand_mentions 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 clearly steers an agent here when the data was already purchased ('already bought ... however old, for free') and points to get_brand_mentions for anything missing or stale. There is no explicit 'when not to use' for the other saved-mentions siblings, but the buy/read split is unambiguous.

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