Skip to main content
Glama

SEOAI - AI Visibility Tracker

List brands

list_brands
Read-onlyIdempotent

Lists the brands tracked in the connected SEOAI workspace, each with its topics (market, language, number of active prompts) and the number of open gaps over the last 30 days. Call this first: every other SEOAI tool needs a brand_id from here (and a topic_id from the topics list when you want to narrow to one topic). Next step: list_gaps with a brand_id, then get_gap_audit for a prompt that has an audit. A gap is a tracked prompt where AI answers did not cite, or rarely cited, the brand (counts come from stored runs). The window field gives the exact period behind open_gaps_30d. limit (default 20, max 100) and offset page through the brands; pagination.next_offset is null on the last page. app_url opens the brand in SEOAI.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoBrands per page. Default 20, max 100.
offsetNoBrands to skip. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, and the description adds substantial context on top: the definition of a gap, that counts derive from stored runs, what window means relative to open_gaps_30d, and that pagination.next_offset is null on the final page. These are semantics an agent cannot get from the annotations or schema.

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?

Purpose and the 'call this first' prerequisite are front-loaded, and no sentence is filler. It is dense for a two-parameter list tool, but every clause carries either routing, semantics, or return information.

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: it lists per-brand topics fields, the gap count, the window field, and app_url. Combined with pagination and sequencing notes, an agent has everything needed to call this correctly on the first try.

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 limit and offset are already documented, and the description largely restates them (default 20, max 100). It does add meaning beyond the schema by explaining the paging mechanism and the terminal condition on pagination.next_offset, which is a return-side field not in the input schema.

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 first sentence names a specific verb and resource ('Lists the brands tracked in the connected SEOAI workspace') and immediately enumerates what each item carries (topics with market, language, active prompt count; open gaps over 30 days). This is clearly distinguishable from siblings like list_gaps or get_gap_audit, which operate on gaps and audits rather than brands.

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?

Explicit routing guidance: 'Call this first: every other SEOAI tool needs a brand_id from here' states a hard prerequisite, and 'Next step: list_gaps with a brand_id, then get_gap_audit for a prompt that has an audit' names the follow-on tools and the condition for each. The topic_id narrowing caveat is also stated.

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