Skip to main content
Glama

Visibility Genies

Look up a brand

lookup_brand

Buys a Brand Lookup for this project, as the Brand Lookup page does (United States, English; ChatGPT and Google AI Overview): how often AI answers mention a brand or domain and its AI search volume on each platform, and, when asked, the pages those answers cite and sample prompts, with Competitor Research against any competitors named. Estimated price: ~$0.44 for the mentions and AI search volume; cited pages ~$0.44 and sample prompts ~$0.80 more; Competitor Research ~$0.44 with 1 competitor, ~$0.44 with 5. What is saved and current, here or on the page, is read free; only the parts missing or out of date (after 24 hours) are bought, as the page's Refresh buys them. It opens free on Brand Lookup and in its History; get_saved_brand_lookup 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>"
    },
    "name": "lookup_brand"
  }
}

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. Ignored when every brand is a domain.
queryYesThe brand or domain to look up, e.g. 'example.com' or 'Example Brand'.
scopeNoFor a domain: the scope to look it 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.
citedPagesNoAlso buy the pages most cited in AI answers that mention it, when the lookup has none saved. Defaults to false.
competitorsNoUp to 5 competitor brands or domains to compare it with (Competitor Research), in any order, bought with it as the page buys a lookup that names them. Omit for the lookup alone; compare_brands buys the comparison alone.
samplePromptsNoAlso buy sample prompts whose AI answers mention it, with how often each is asked, when the lookup has none saved. Defaults to false.
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
queryYes
boughtYes
lookupYes
competitorsYes
savedResultIdNo
accountRefusalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the spend envelope: per-call hold of estimate plus margin, the workspace agent spend limit ($2.00 default), refusal before any purchase, and the actual charge being what was bought. This is billing-relevant behavior the readOnlyHint=false and destructiveHint=false flags cannot convey. Minor gap: it never says whether a refused call has side effects beyond the hold, but the pre-purchase refusal is stated clearly.

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?

Front-loaded with purpose, which is good, but the remainder is a dense run-on paragraph mixing pricing, cache/staleness rules, spending limits, and the approval flow. The price sentence ("~$0.44 with 1 competitor, ~$0.44 with 5") and the free-read explanation could be tightened without losing decision-relevant content.

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 an eight-parameter, costly, non-read-only tool with an output schema, the description covers everything an agent needs to decide and call correctly: what is bought, what is free, staleness window, price estimate, spend-limit refusal, and the approval parameter. Return values are properly left to the output schema.

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 eight parameters; the description's added value is cost semantics tied to optional parameters (cited pages ~$0.44, sample prompts ~$0.80, Competitor Research ~$0.44 with 1 vs 5 competitors). It does not separately explain names or scope, which the schema handles.

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 ("Buys a Brand Lookup for this project") and immediately scopes it to the exact page behavior (United States, English; ChatGPT and Google AI Overview) plus the outputs it produces. It also differentiates itself from siblings by naming get_saved_brand_lookup for the free read and compare_brands for the comparison-only purchase.

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?

Explicitly separates buying from reading ("What is saved and current... is read free; only the parts missing or out of date (after 24 hours) are bought") and routes the agent to get_saved_brand_lookup when nothing should be purchased. It also gives the exact escalation path when a call is refused: ask the user, then retry with approvedMaxCostUsd.

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