Skip to main content
Glama

Visibility Genies

Read a saved brand comparison

get_saved_brand_comparison
Read-only

Reads Brand Lookup's Competitor Research already bought for this project, however old, for free: a brand and its competitors side by side in AI answers (United States, English; ChatGPT and Google AI Overview), each one's mentions and AI search volume on each platform, and its Share of Voice. It never buys: what is not saved is named with the price compare_brands 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>",
      "query": "<query>",
      "competitors": "<competitors>"
    },
    "name": "get_saved_brand_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNoFor a comparison of domains beside brand names, which compares every brand by name: the name to compare a domain by, keyed by the domain, e.g. {"bestbuy.com": "Best Buy"}. A domain left out is compared by the words it spells, capitalised ("Bestbuy", "Acme Shoes" for acme-shoes.com). Ignored when every brand is a domain.
queryYesThe brand or domain to compare, usually the project's own, e.g. 'example.com' or 'Example Brand'.
scopeNoFor a domain: the scope it is looked up with on Brand Lookup. Omit to derive it from the query, as the page does. The comparison itself always compares whole domains.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
competitorsYes1 to 5 competitor brands or domains, in any order.

Output Schema

NameRequiredDescriptionDefault
metaNo
queryNo
savedNo
comparisonNo
competitorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses the cost model (free, never purchases), the staleness tolerance ('however old'), the fixed geographic/language/platform coverage, and the partial-result behavior (missing items are named with the price the buying tool would pay). Those are exactly the facts an agent needs to decide whether the saved snapshot is good enough or a paid refresh is warranted.

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 verb and the free/stale framing before the payload details and the compare_brands contrast. It is dense but each clause carries distinct information. Minor cost: 'already bought ... however old, for free' is an awkward stack of qualifiers that takes a second read.

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?

An output schema exists, so return shape need not be spelled out, yet the description still summarizes what comes back and what happens when a piece is missing. Together with the annotations it covers cost, coverage, freshness and fallback for a five-parameter read tool, leaving no decision-relevant gap.

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% and the schema itself documents query, competitors, scope, names and projectId in depth, so the schema already carries the parameter burden. The description only reinforces that the comparison is brand-plus-competitors and that the result is side-by-side; it adds nothing about the tricky 'names' mapping or the scope enum. Baseline 3 is appropriate.

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?

Specific verb and resource: reads a saved brand comparison, and it names the exact payload (brand vs competitors side by side in AI answers on ChatGPT and Google AI Overview, mentions, AI search volume, Share of Voice). The closing clause explicitly separates it from compare_brands, so an agent can pick between them 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?

States the operative condition well: this tool only reads what is already bought, including stale data, and never buys; anything not saved is reported with the price compare_brands would charge. That effectively routes the agent to the alternative. It stops short of an explicit 'use compare_brands when X' instruction and never distinguishes itself from the sibling get_saved_domain_comparison.

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