Skip to main content
Glama

Visibility Genies

Compare brands

compare_brands

Brand Lookup's Competitor Research: a brand and 1 to 5 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. Estimated price: up to $0.44 for 5 competitors, up to $0.44 for 1: one AI mentions request per platform for every brand. A comparison saved within 24 hours, here or on the Brand Lookup page, is read free. It opens free on Brand Lookup; get_saved_brand_comparison 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>",
      "query": "<query>",
      "competitors": "<competitors>"
    },
    "name": "compare_brands"
  }
}

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.
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
queryNo
savedNo
comparisonNo
competitorsNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false; the description goes well beyond that. It discloses pricing per competitor count, that a call may spend up to the workspace agent spend limit without asking, that funds are held at estimate plus margin and charged for what was bought, and that over-limit calls are refused before purchase with the estimate and maximum returned.

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?

The purpose is front-loaded in the first clause, which is good, but the pricing sentence is convoluted and repetitive ('up to $0.44 for 5 competitors, up to $0.44 for 1') and the spend-limit mechanics are packed into one long run-on. The information earns its place, but the packaging is denser than it needs to be.

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 paid, open-world comparison tool with an output schema, the description covers cost, saving, free re-reads, and the approval path, which is what an agent needs to call it safely. Edge cases like how names and scope interact are left entirely to the schema, which is acceptable given 100% coverage.

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 baseline is 3, but the description adds real meaning beyond the schema for approvedMaxCostUsd: it is only needed after a refusal, must reflect what the user approved, and must never be set without asking. It also ties the competitor count to the cost estimate, which the schema does not do.

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?

The description names a specific verb and resource: it puts a brand and 1-5 competitors side by side in AI answers and returns mentions, AI search volume per platform, and Share of Voice. That is far more concrete than the title. It does not explicitly distinguish itself from the sibling compare_domains, so it stops 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?

It gives clear operating context: a comparison saved within 24 hours is read free, and get_saved_brand_comparison reads it without buying, which tells the agent when not to re-run this tool. It also spells out the refusal/approval loop for approvedMaxCostUsd. It never states when to prefer compare_domains or another sibling, so it is not a full 5.

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