Skip to main content
Glama

Visibility Genies

Get brand mentions

get_brand_mentions

Brand Mentions' tone and trend for a brand on the web (the data service's content analysis), the project's own site left out: the sites that write about it most positively, negatively and neutrally, how often it is mentioned month by month for 12 months, and the spread of ratings on pages that rate it. Estimated price up to $0.18, billed by the rows returned. The web pages that name a brand, and their totals, are get_web_mentions'. Mentions the Brand Mentions page bought are listed too, free. A part saved within 24 hours, here or on the page, is read free; get_saved_brand_mentions reads it without buying. 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_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.
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
savedNo
keywordNo
summaryNo
mentionsNo
excludeDomainNo
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 say readOnlyHint=false and openWorldHint=true; the description supplies the whole commercial contract: estimated price up to $0.18, billed by rows returned, a $2.00 workspace spend ceiling, a hold of estimate plus margin during the run, and refusal before purchase when the maximum exceeds the limit. It also discloses that previously purchased parts and parts saved within 24 hours are read free, which is non-obvious behavior an agent could not infer from the annotations.

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 scope and the sibling contrast come first, then cost mechanics, then the free-read carve-out — a sensible front-loaded order. Some phrasing is dense and slightly awkward ("'Brand Mentions' tone and trend", "Mentions the Brand Mentions page bought are listed too, free"), but no sentence is filler given how much commercial behavior must be conveyed.

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, non-read-only call with an output schema, the description covers the pieces that matter: what is returned, what is excluded, what is free, what it costs, and how to recover from a spend-limit refusal. Nothing an agent needs in order to call it correctly or safely 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 schema already documents all four parameters, and the description mostly reinforces that. It does add context the schema does not carry on its own: the exclusion of the project's own site is framed as the default behavior, and the approvedMaxCostUsd parameter is embedded in the refusal/approval workflow (estimate plus maximum shown, then user approval) rather than left as an isolated field.

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 names a specific resource and the exact content returned: tone and trend for a brand, most positive/negative/neutral sites, monthly mention counts over 12 months, and rating spread. It explicitly draws the boundary against get_web_mentions ("The web pages that name a brand, and their totals, are get_web_mentions'") and against get_saved_brand_mentions, so an agent can pick it without opening a schema.

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?

It names the sibling alternatives and the conditions that select them: get_web_mentions for raw page lists and totals, get_saved_brand_mentions when a part was already bought within 24 hours. It also prescribes the escalation path for an over-limit call — ask the user, then re-call with approvedMaxCostUsd — which is explicit when-to-use guidance for the fourth parameter.

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