Skip to main content
Glama

List generations

list_generations
Read-onlyIdempotent

List your generation runs, newest first, optionally for one project. Each run has mode: full (rendered thumbnails) or concept (text-only titles, hooks and briefs). Use to find "my last one" or earlier text-only ideas, then show_thumbnails (full) or get_generation (concept). Follow nextCursor for older runs.

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
limitNo
cursorNo
projectIdNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / mode
      Added value: +{
      +  "enum": [
      +    "full",
      +    "concept"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the description correctly spends its words elsewhere: result ordering, the full vs concept distinction and what each mode contains (thumbnails vs titles/hooks/briefs), and cursor-based pagination. It does not mention page size limits or cursor expiry/invalid-cursor behavior, which would round out the picture.

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 compact sentences, front-loaded with the resource and ordering, then mode semantics, then routing. Every clause carries operational information and there is no filler.

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?

An output schema exists, so return values need not be spelled out, and the description still covers ordering, the mode field and pagination. The main gap is the undocumented limit parameter and its default, which an agent would have to read from the schema.

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 0%, so the description must carry parameter meaning. It explains projectId ("optionally for one project") and cursor ("Follow nextCursor for older runs") well, but says nothing about limit or its default of 20, leaving one of three parameters undocumented in both places.

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?

States a specific verb and resource ("List your generation runs") plus ordering ("newest first") and scope ("optionally for one project"). It also explains the two run modes and which sibling handles each, so an agent can distinguish this from get_generation and show_thumbnails without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ("find 'my last one' or earlier text-only ideas") and routes onward: show_thumbnails for full runs, get_generation for concept runs. It also states how to continue pagination ("Follow nextCursor for older runs"), leaving little to inference.

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