Skip to main content
Glama

List generations

list_generations
Read-onlyIdempotent

List your past generations, newest first, with each output's media ID and link. Outputs deleted since stay listed with available false. Use get_generation for a generation that is still running.

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_generations"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOutput medium to use when filtering generation history.
limitNoNumber of matching items to include on this page. Omit to return 20 items.
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.
brand_session_idNoBrand whose generation history to retrieve. Use its Brand session ID from list_brands; omit to leave results unfiltered by brand.

Output Schema

NameRequiredDescriptionDefault
has_moreYesWhether more results follow this page.
generationsYesGenerations on this page, newest first.
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

A4.3/5.0
Behavior4/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 covered. The description adds genuinely new context beyond that: ordering is newest-first, deleted outputs remain in the listing flagged with available=false, and each item carries a media ID and link. Pagination behavior is left to the schema.

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, each earning its place: what it returns, how deletions are surfaced, and the alternative tool. The most useful fact (scope and ordering) is front-loaded with no filler.

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

Completeness5/5

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

With an output schema present, return-shape explanation is unnecessary, and the description still flags the non-obvious available=false semantics for deleted items. Five optional parameters and pagination are fully handled by the schema, so nothing critical is missing for correct invocation.

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 type, limit, cursor, llm_model and brand_session_id are all documented in structured data. The description adds no parameter-level detail beyond implying history retrieval; baseline 3 applies when the schema does the heavy lifting.

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 your past generations'), then adds ordering ('newest first') and return content ('media ID and link'), so an agent knows exactly what it gets. It also separates itself from get_generation by reserving that tool for still-running generations.

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 one explicit routing rule: use get_generation when the generation is still running. It does not address when to prefer this over the sibling per-medium listers (list_images, list_videos, list_audio), leaving that inference to the agent, but the guidance it does give is unambiguous.

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