Skip to main content
Glama

Visibility Genies

Get brand performance

get_brand_performance

Brand Performance: for a topic or keyword, the up to 100 brands ChatGPT's answers mention most, with their mentions, AI search volume and Share of Voice, the brand categories they mention most, and where a brand stands among them (United States, English; ChatGPT: the only market and platform with brand data). Estimated price: up to $0.64, one AI mentions request for the brands and one for the categories, billed by the rows they return. A topic saved within 24 hours, here or on the Brand Performance page, is read free. It opens free on that page; get_saved_brand_performance 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>",
      "topic": "<topic>"
    },
    "name": "get_brand_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoThe brand to find among them. Omit for the project's, named by its domain without the ending.
topicYesA topic or keyword, e.g. 'crm software'.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
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
savedNo
topicNo
brandsNo
categoriesNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations, it discloses cost structure (up to $0.64, billed per returned row, two requests), the workspace spend limit default of $2.00, that funds are held at estimate plus margin and never overcharged, that over-limit calls are refused before purchase, and that a freshly saved topic is free. These are exactly the operational facts an agent needs before spending money, none of which appear in the annotations.

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?

It is front-loaded with the capability and scope before the pricing detail, and nearly every sentence carries needed information. There is mild redundancy around the free-saved-topic rule, which is stated twice in slightly different wording, and the single paragraph is dense, but nothing is wasted at the level of substance.

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?

Return values are covered by the output schema, so the description only needed to cover scope, cost, billing behavior and the refusal path — and it does all of that, including the market/platform restriction that would otherwise surprise an agent. Nothing material for correct invocation is missing.

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: 'brand' defaults to the project's own brand named by its domain, and approvedMaxCostUsd is positioned as the post-refusal escalation path with an explicit instruction to ask the user first and never set it unprompted. That procedural context is not in the schema text.

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?

The description opens with a concrete verb and resource: the up to 100 brands ChatGPT's answers mention most for a topic, plus the metrics returned (mentions, AI search volume, Share of Voice, brand categories, rank among them). It also pins the scope (United States, English, ChatGPT only), which lets an agent tell it apart from the sibling brand tools without opening a 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?

It gives a clear routing rule: a topic saved within 24 hours is free, and get_saved_brand_performance reads it without buying, which tells the agent when this paid call is unnecessary. It also spells out the refused-call recovery path (ask the user, then retry with approvedMaxCostUsd). It stops short of explicitly saying 'prefer the saved variant when the topic already exists', leaving that inference to the agent.

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