Skip to main content
Glama

Visibility Genies

Read saved brand performance

get_saved_brand_performance
Read-only

Reads Brand Performance already bought for a topic in this project, however old, for free: the brands and brand categories ChatGPT's answers about it mention most (United States, English; ChatGPT), and where a brand stands among them. It never buys: what is missing or out of date is named with the price get_brand_performance would pay for it.

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_saved_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.

Output Schema

NameRequiredDescriptionDefault
metaNo
savedNo
topicNo
brandsNo
categoriesNo

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?

Beyond the readOnly/destructive/openWorld annotations, it discloses cost behavior (free, never spends credits), staleness tolerance ('however old'), and the side effect of naming missing or out-of-date items with their price. That is exactly the kind of billing and freshness context annotations cannot express.

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-loads what is read and its free/stale-tolerant nature, but the single run-on construction with nested parentheses ('(United States, English; ChatGPT)') and the second sentence's 'It never buys' framing takes effort to parse. Every clause carries information, though, so little is wasted.

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 a read-only, 3-parameter tool with an output schema, the description covers scope, cost, freshness, fallback behavior when data is missing, and the alternative for buying. Nothing an agent needs in order to call it correctly and predict its cost is missing.

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%, including the note that brand defaults to the project's brand named by its bare domain and that projectId requires list_projects. The description only echoes 'a topic' and 'a brand' without adding format or default semantics beyond the schema, so the baseline of 3 applies.

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 ('Reads Brand Performance already bought for a topic in this project') plus the exact returned content: the brands and brand categories mentioned most, and a brand's rank among them. It also names the source/scope (United States, English; ChatGPT), which is enough for an agent to distinguish it from get_brand_performance.

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?

Gives an explicit selection rule: this tool reads already-purchased data 'for free' and 'never buys', while missing or stale data is only named with the price that get_brand_performance would pay. The alternative tool is named with the condition that selects it, so the agent knows both when to use this and when to switch.

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