Skip to main content
Glama

Visibility Genies

Read a saved brand lookup

get_saved_brand_lookup
Read-only

Reads a Brand Lookup already bought for this project: how ChatGPT and Google's AI Overviews mention a brand or domain in the United States, and Share of Voice against the competitors it compared (get_saved_brand_comparison shows its Competitor Research). The pages they cite and sample prompts are bought on their own, so a lookup has them only when they were. Uses no credits and never buys: what is not saved or out of date is named with the price Brand Lookup asks for it, each of those two parts at its own. lookup_brand buys them at that price, as the page does, and compare_brands buys Competitor Research alone.

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>"
    },
    "name": "get_saved_brand_lookup"
  }
}

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, as it was looked up on the Brand Lookup page.
scopeNoFor a domain: the scope it was looked up with. Omit to derive it from the query, as the page does.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
competitorsNoThe competitors its Share of Voice compared, if any, in any order.

Output Schema

NameRequiredDescriptionDefault
metaNo
toBuyYes
lookupYes
addOnsToBuyYes
toBuyPriceUsdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, so the safety profile is covered. The description adds genuinely useful behavior beyond that: no credit consumption, no purchases, per-part pricing surfaced for anything unsaved or out of date, and the fact that cited pages and sample prompts are only present when bought separately. It does not describe pagination or result formatting, but an output schema exists to carry return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences, but both are long, comma-heavy run-ons with garbled phrasing such as "each of those two parts at its own." The read-only/no-credit guarantee — the most decision-relevant fact — is placed mid-paragraph rather than front-loaded. Content is dense and mostly earns its place, but the packaging costs readability.

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?

For a read tool with annotations, a full output schema, and complete schema coverage, the description supplies the remaining decision-relevant context: scope of data, pricing/billing behavior on missing parts, and how it relates to lookup_brand and get_saved_brand_comparison. What is missing is minor — no mention of what an empty or partial result looks like in practice.

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 all five parameters including the nested names map and the scope enum are already documented in the schema. The description adds only a light framing that the query mirrors "as it was looked up on the Brand Lookup page" and that cited-pages/prompt data is conditional. Baseline 3 is appropriate since the schema does the heavy lifting for parameters like names and competitors.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Reads a Brand Lookup already bought for this project") and enumerates the contents it covers: ChatGPT and Google AI Overviews mentions for a brand or domain in the United States plus Share of Voice against competitors. It explicitly names the sibling that covers a different slice ("get_saved_brand_comparison shows its Competitor Research"), so an agent can separate the two. The prose is roundabout and buries the core purpose behind several clauses, which keeps it short of a 5.

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?

Gives clear conditions for use: it is a read of already-purchased data that "Uses no credits and never buys," and it explains what happens when data is missing or stale — those parts are named along with the price Brand Lookup charges. It also points to alternatives, noting that "lookup_brand buys them at that price" and "compare_brands buys Competitor Research alone." It does not phrase an explicit directive rule ("use lookup_brand if not saved"), leaving the routing inference to the reader.

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