Skip to main content
Glama

Modern AI Brand Recommendation Rate

Look up a brand's AI Recommendation Rate

lookup_brand_recommendation_rate
Read-only

Look up a brand's AI Recommendation Rate: the percentage of buyer-intent questions where AI search picks the brand first, not just mentions it. Also returns its Recommendation Inclusion Rate: how often the brand appears anywhere in the answer. Measured on ChatGPT with search enabled, refreshed monthly. Use it to check a brand's generative engine optimization (GEO) or AI search visibility, or how visible a brand is when AI answers recommend products. Returns the brand's public record URL and measured date for citation, plus its company profile (each fact with its source link) when one is published. Free, one brand per call, rate-limited per Modern AI's published anti-scrape policy.

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": {
      "brand": "<brand>"
    },
    "name": "lookup_brand_recommendation_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand name to look up, e.g. "Brumate"

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?

Goes well past the readOnlyHint/openWorldHint annotations: discloses the data source and cadence ('Measured on ChatGPT with search enabled, refreshed monthly'), cost and quota model ('Free, one brand per call, rate-limited per Modern AI's published anti-scrape policy'), and the citation fields returned. An agent knows the freshness, scope, and limits before calling.

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?

Front-loaded with the core metric definition, then the secondary metric, then measurement provenance, then use cases, then return/cost details — a sensible priority order with no filler sentences. Sentences are long and clause-dense (the first sentence packs a definition and a contrast), which costs a point on scannability.

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?

With no output schema, the description carries the return-value burden and does so: the primary rate, the inclusion rate, the public record URL and measured date for citation, and conditional company profile facts with sources. Combined with data provenance and quota disclosure, an agent has everything needed to call and interpret results.

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 single `brand` parameter already has an example, so the schema does the heavy lifting. The description adds only the 'one brand per call' cardinality constraint; it does not clarify matching behavior (exact vs fuzzy name, what happens on ambiguous or unknown brands), which is the real ambiguity for a name-string lookup.

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?

Specific verb 'look up' plus a precisely defined resource, with the metric unpacked ('percentage of buyer-intent questions where AI search picks the brand first, not just mentions it') and a second metric (Recommendation Inclusion Rate) explicitly distinguished. It does not name the sibling get_recommendation_rate_methodology, so an agent must infer where methodology questions go, which keeps it just 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 use contexts: checking a brand's GEO/AI search visibility, or how visible a brand is when AI answers recommend products. It stops short of explicit exclusions or naming the alternatives (e.g. the methodology tool for 'how is this computed' questions), so it lacks the when-not guidance a 5 requires.

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.