Skip to main content
Glama

List brands

list_brands
Read-onlyIdempotent

List brands with published launch films. Includes no logos or brand media files. A brand that only has clips is not listed; its clips are found through search_scenes and get_brand.

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
queryNo
cursorNo
industryNo

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return scope (brands only, no logos or media files) and the filtering rule that clip-only brands are omitted — a behavioral trait an agent would otherwise discover only by inspecting results.

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?

Three short sentences, front-loaded with the purpose, followed by return-scope and exclusion rules. No filler, no restatement of the title, and each sentence carries decision-relevant information.

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

Completeness3/5

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

Because an output schema exists and annotations cover safety and idempotency, the description need not explain return values or side effects, and it handles brand-inclusion semantics well. What is missing is any treatment of the four filter/pagination parameters, which is the main thing an agent still needs in order to call this correctly.

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?

All four parameters (limit, query, cursor, industry) have 0% schema description coverage, so the schema supplies types and bounds but no meaning. The description compensates for none of them: it never explains what 'query' matches, what values 'industry' accepts, or how cursor paging works. With four undocumented parameters, this is a significant gap rather than a minor one.

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 and resource ('List brands') and immediately narrows scope to those 'with published launch films', so the agent knows this is a filtered enumeration rather than a full brand dump. It also states the negative scope (no logos or brand media files) and names the siblings (search_scenes, get_brand) that cover what is excluded, making it distinguishable from those 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 explicit when-not guidance: a brand that only has clips is not listed, and its clips must be reached via search_scenes and get_brand. That is concrete routing. It stops short of saying when to prefer get_brand for a single known brand versus listing, and offers no guidance on query/industry filtering, so it is not fully exhaustive.

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