Skip to main content
Glama

List brands

list_brands

List the brands of the API key's workspace with the accounts (id, channel) attached to each and whether the owner requires approval. Requires scope ACCOUNTS_READ.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present the description must carry the burden, and it does disclose two real behavioral facts: authorization requires scope ACCOUNTS_READ, and results are implicitly scoped to the API key's workspace rather than caller-supplied. It omits pagination, result-size limits, and ordering, which matter for a zero-parameter list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence states the resource, its scope, the returned fields, and the required permission in that order. No filler, no repetition of the title, nothing an agent has to skip.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, parameterless read tool with no output schema, the description usefully sketches the return payload (accounts with id and channel, approval requirement) and the auth scope. It stops short of describing pagination or the full response envelope, which is the remaining gap.

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?

The tool takes zero parameters, so the schema carries nothing to explain and the baseline is 4; however, the description's only semantic addition is that scoping comes from the API key, which is thin even for an argument-less tool. Nothing is misleading, but little is added beyond the fact that no filters exist.

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?

States a specific verb and resource ('List the brands') and adds scope ('of the API key's workspace') plus the payload each brand carries (accounts with id, channel, approval flag). It does not explicitly distinguish itself from list_accounts or other list_* siblings, so an agent must infer the brand-vs-account distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: it is a read-only listing of brands scoped to the workspace of the calling key. There is no statement of when to prefer it over list_accounts or how it fits a brand-then-account discovery workflow, and no exclusions.

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