Skip to main content
Glama

List Brand Versions

list_brand_versions
Read-onlyIdempotent

List saved versions of a brand, including which version is latest. Returns each version's ID and creation time. Pass a version_id to get_brand or view_files to read that version.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_session_id": "<brand_session_id>"
    },
    "name": "list_brand_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of saved versions to include on this page. Omit to return 50 versions.
cursorNoContinuation token from this brand's previous list_brand_versions result. Pass its next_cursor to retrieve 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.
brand_session_idYesBrand session ID from `list_brands`.

Output Schema

NameRequiredDescriptionDefault
has_moreYesWhether more results follow this page.
versionsYesSaved versions on this page.
next_cursorYesPass as cursor to get the next page. Null when no more results follow.
brand_session_idYesBrand session ID the versions belong to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the shape of each returned entry (ID, creation time, latest marker) and the workflow to consume a version, but says nothing about pagination limits or ordering beyond what the schema and output schema already carry.

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, zero filler, with the core purpose and the return contents front-loaded before the follow-up routing. Every sentence contributes something the agent needs.

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 rich annotations, a full output schema, and 100% schema coverage, this simple read tool needs little more. The only gap is that pagination behavior is left entirely to the schema rather than mentioned in prose, which is minor here.

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%, so limit, cursor, brand_session_id, and llm_model are all documented in the schema itself (including the 50-version default and next_cursor continuation). The description adds no parameter meaning beyond that, which is the correct baseline for a fully documented schema.

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?

The description names a specific verb and resource ('List saved versions of a brand') and adds scope detail ('including which version is latest', returning IDs and creation times). It also distinguishes this tool's output from the read path by routing to get_brand/view_files, though it doesn't contrast against other listing siblings on the same resource.

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?

It gives a clear follow-up instruction ('Pass a version_id to get_brand or view_files to read that version'), which implies this tool is the enumeration step before reading a specific version. However, it never states when not to use this tool or which sibling to prefer if you only need the current brand state.

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