Skip to main content
Glama

Your brands

list_brands
Read-onlyIdempotent

Your brands: id, name, whether it is your default, whether it has shared social accounts, and its colours and style in brief. Pass an id as brandId when generating to apply its look, as workspaceBrandId to file the result under the brand, or as brandId in list_media and schedule_post. Deleted brands are not listed.

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
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses that deleted brands are excluded and lists the returned fields, which is genuinely useful context. It does not describe pagination behavior or how the limit parameter interacts with results, leaving a minor behavioral gap.

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?

The description is compact and front-loaded: returned fields first, then practical id usage, then the deletion caveat. Every sentence carries useful information, though the middle sentence is dense with multiple parameter mappings.

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 read-only list tool with no output schema, the description supplies the returned fields, deletion behavior, and cross-tool id usage. The main gap is the unexplained limit parameter, but the schema itself supplies its bounds and default.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0% for the single limit parameter, and the description never mentions limit, pagination, or what happens when more brands exist than the limit. Since low coverage requires the description to compensate, this is a meaningful omission.

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 specific verb/resource ('Your brands') and enumerates exactly what each item contains: id, name, default status, shared social accounts, colours and style. This lets an agent distinguish it from siblings like list_media or list_characters without opening the 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 clear downstream usage guidance: pass the id as brandId when generating, as workspaceBrandId to file results, and as brandId in list_media and schedule_post. It does not explicitly say when not to use this tool versus alternatives, but the scope is clear enough for correct selection.

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