Skip to main content
Glama

List Brands

list_brands
Read-onlyIdempotent

List brands you can access, including their Brand session IDs, names, statuses, and workspaces.

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
urlNoFilter brands by website URL (partial match, e.g. "gumroad.com")
limitNoNumber of accessible Brands to include on this page. Omit to return 50 Brands.
cursorNoPass next_cursor from the previous result to get the next page.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
workspace_idNoScope results to one workspace by id (from list_workspaces). Omit (or pass null) to span every workspace the caller can see — each result is labeled with its workspace.

Output Schema

NameRequiredDescriptionDefault
brandsYesBrands on this page.
has_moreYesWhether more results follow this page.
next_cursorYesPass as cursor to get the next page. Null when no more results follow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the permission-scoping nuance ('brands you can access') and the returned field set, but says nothing about pagination behavior or the analytics-only llm_model parameter's effect.

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?

A single front-loaded sentence with no wasted wording. It is efficient, though it is perhaps too terse to carry usage guidance.

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?

With an output schema, full annotation coverage, and 100% schema description coverage, the description only needs to establish purpose and access scope, which it does. The minor gap is the absence of any routing hint toward sibling tools.

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 description coverage is 100%, including url, limit, cursor, workspace_id, and llm_model, so the schema carries parameter meaning fully. The description adds no parameter detail beyond what the schema already documents, making baseline 3 appropriate.

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 brands') plus the scope ('you can access') and enumerates returned fields (session IDs, names, statuses, workspaces). It does not, however, contrast itself with siblings like get_brand or list_brand_versions, so an agent gets no explicit differentiation.

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: the phrase 'brands you can access' hints at an enumeration/scope-listing scenario, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as get_brand for a single brand.

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