Skip to main content
Glama

list_recent_generations

Read-onlyIdempotent

List your recent successful generations and return their download URLs again. Use this to recover a generation whose result message was lost (for example a dropped connection mid-call): generations are billed when they complete, and their downloads stay available until their original expiry even if the response never arrived - re-listing does not extend the expiry. Generations made on the logospell.com generate page appear here too. Returns, newest first: each generation's id, creation and expiry times, zip download URL, its set lineage (parent generation ids plus the style-reference sources it was made with, ready to reuse via create_reference), and promptJSON - the batch's own prompt.json, whose style and subject descriptions are the original call, so a past generation can be reproduced rather than only identified, and whose delivery levers follow the set's current delivery once it has been edited. Costs no credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of recent generations to return (default 5). There is no ceiling: pass a large number to list everything, and read total in the output to know whether anything was left out.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYesHow many unexpired generations this key has in all. Greater than the number of rows returned means the listing was cut short by limit; ask again with a larger limit.
generationsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / properties / generations / items / properties / promptJSON / description
      Previous value: -"The original call, verbatim, exactly as the batch's own prompt.json records it - the same bytes that ship inside the zip. Its shape follows the tool named in its own tool field. Sets carry style, subjects as {description, filename} pairs, format, quality, minimumMargin, validation, width and height when an axis was fixed, background for solid-background sets, and styleReferences as zip-relative paths when the call used them. Illustrations carry prompt, width, height, format, quality and filename. Read subjects[].description to reproduce a set: a subject given in object form has a description that differs from its filename, so search.webp may have been asked for as a magnifying glass."New value: +"The batch's own prompt.json, verbatim - the same bytes that ship inside the zip. Its style, subjects and styleReferences are the original call and no edit can change them; its delivery levers (width, height, canvas, minimumMargin, format, quality, background) are the batch's current delivery, which edit_image_set rewrites, so reusing this reproduces the set as it stands now rather than as first delivered. The edited flag says whether that has happened. Its shape follows the tool named in its own tool field. Sets carry style, subjects as {description, filename} pairs, format, quality, minimumMargin, validation, width and height when an axis was fixed, background for solid-background sets, and styleReferences as zip-relative paths when the call used them. Illustrations carry prompt, width, height, format, quality and filename. Read subjects[].description to reproduce a set: a subject given in object form has a description that differs from its filename, so search.webp may have been asked for as a magnifying glass."
  2. Changed8 schema fields changed
    • addedOutput schema / properties / generations / items / properties / deliveredAt
      Added value: +{
      +  "description": "When the current delivery was cut: the generation time, or the time of the last edit_image_set.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / generations / items / properties / editable
      Added value: +{
      +  "description": "True when this set can be re-delivered with edit_image_set (it has a source to cut from).",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / generations / items / properties / edited
      Added value: +{
      +  "description": "True when edit_image_set has changed this set's delivery from what was generated; a reset makes it false again.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / generations / items / properties / iconCeiling
      Added value: +{
      +  "description": "The largest base size, in pixels, at which export_icons keeps every density of this set crisp (no subject enlarged past its source pixels) at its current levers; absent when no base size does. Fixed by the subject count at generation; edits to margin or sizing move it.",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / generations / items / properties / levers
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "The delivery levers now in force for a set (width, height, minimumMargin, format, quality, background): the first delivery's until edit_image_set changes them. Absent on illustrations and on sets from before editing existed.",
      +  "properties": {
      +    "background": {
      +      "type": "string"
      +    },
      +    "canvas": {
      +      "type": "string"
      +    },
      +    "format": {
      +      "type": "string"
      +    },
      +    "height": {
      +      "type": "integer"
      +    },
      +    "minimumMargin": {
      +      "type": "integer"
      +    },
      +    "quality": {
      +      "type": "integer"
      +    },
      +    "sizing": {
      +      "type": "string"
      +    },
      +    "width": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "minimumMargin",
      +    "format"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
    • addedOutput schema / properties / generations / items / properties / nativeHeight
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / generations / items / properties / nativeWidth
      Added value: +{
      +  "description": "The canvas this set would be delivered on at native size (its trimmed frame plus margin): the size any re-delivery compares against.",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / generations / items / properties / promptJSON / description
      Previous value: -"The original call, verbatim, exactly as the batch's own prompt.json records it - the same bytes that ship inside the zip. Its shape follows the tool named in its own tool field. Sets carry style, subjects as {description, filename} pairs, format, quality, minimumMargin, validation, size when one was requested, background for solid-background sets, and styleReferences as zip-relative paths when the call used them. Illustrations carry prompt, width, height, format, quality and filename. Read subjects[].description to reproduce a set: a subject given in object form has a description that differs from its filename, so search.webp may have been asked for as a magnifying glass."New value: +"The original call, verbatim, exactly as the batch's own prompt.json records it - the same bytes that ship inside the zip. Its shape follows the tool named in its own tool field. Sets carry style, subjects as {description, filename} pairs, format, quality, minimumMargin, validation, width and height when an axis was fixed, background for solid-background sets, and styleReferences as zip-relative paths when the call used them. Illustrations carry prompt, width, height, format, quality and filename. Read subjects[].description to reproduce a set: a subject given in object form has a description that differs from its filename, so search.webp may have been asked for as a magnifying glass."
  3. Changed7 schema fields changed
    • removedOutput schema / properties / generations / items / properties / images
      Removed value: -{
      -  "type": "integer"
      -}
    • removedOutput schema / properties / generations / items / properties / names
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": [
      -    "null",
      -    "array"
      -  ]
      -}
    • addedOutput schema / properties / generations / items / properties / promptJSON
      Added value: +{
      +  "description": "The original call, verbatim, exactly as the batch's own prompt.json records it - the same bytes that ship inside the zip. Its shape follows the tool named in its own tool field. Sets carry style, subjects as {description, filename} pairs, format, quality, minimumMargin, validation, size when one was requested, background for solid-background sets, and styleReferences as zip-relative paths when the call used them. Illustrations carry prompt, width, height, format, quality and filename. Read subjects[].description to reproduce a set: a subject given in object form has a description that differs from its filename, so search.webp may have been asked for as a magnifying glass."
      +}
    • removedOutput schema / properties / generations / items / properties / style
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / generations / items / properties / styleReferences / description
      Previous value: -"The style references this generation was made with, in call order, each identified by the delivered image it came from when known. Absent when no references were used."New value: +"The style references this generation was made with, in call order, each identified by the delivered image it came from when known, and reusable via create_reference. Distinct from promptJSON.styleReferences, which records the same references as zip-relative paths inside the original call. Absent when no references were used."
    • removedOutput schema / properties / generations / items / properties / tool
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / generations / items / required
      Previous value: -[
      -  "id",
      -  "tool",
      -  "created",
      -  "expiresAt",
      -  "images",
      -  "zipURL"
      -]New value: +[
      +  "id",
      +  "created",
      +  "expiresAt",
      +  "zipURL",
      +  "promptJSON"
      +]
  4. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of recent generations to return (default 5, max 20)."New value: +"Maximum number of recent generations to return (default 5). There is no ceiling: pass a large number to list everything, and read total in the output to know whether anything was left out."
    • addedOutput schema / properties / total
      Added value: +{
      +  "description": "How many unexpired generations this key has in all. Greater than the number of rows returned means the listing was cut short by limit; ask again with a larger limit.",
      +  "type": "integer"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "generations"
      -]New value: +[
      +  "generations",
      +  "total"
      +]
  5. Changed4 schema fields changed
    • addedOutput schema / properties / generations / items / properties / id
      Added value: +{
      +  "description": "The generation's id - the random segment of its download URLs, accepted by create_reference's sourceGeneration.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / generations / items / properties / parents
      Added value: +{
      +  "description": "Ids of the generations whose delivered images seeded this one's style references - the set lineage. Absent when this generation extended nothing.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • addedOutput schema / properties / generations / items / properties / styleReferences
      Added value: +{
      +  "description": "The style references this generation was made with, in call order, each identified by the delivered image it came from when known. Absent when no references were used.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "from": {
      +        "description": "The generation id this reference image came from; accepted by create_reference's sourceGeneration.",
      +        "type": "string"
      +      },
      +      "image": {
      +        "description": "The delivered image filename inside that generation; accepted by create_reference's sourceImage.",
      +        "type": "string"
      +      },
      +      "uploaded": {
      +        "description": "True for a hand-uploaded reference that came from no generation.",
      +        "type": "boolean"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • changedOutput schema / properties / generations / items / required
      Previous value: -[
      -  "tool",
      -  "created",
      -  "expiresAt",
      -  "images",
      -  "zipURL"
      -]New value: +[
      +  "id",
      +  "tool",
      +  "created",
      +  "expiresAt",
      +  "images",
      +  "zipURL"
      +]
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds significant behavioral nuance: re-listing does not extend expiry, generations are billed when they complete, and downloads remain available even if the response never arrived. This goes well beyond the structured hint data and is consistent with it.

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?

The description is long but every sentence earns its place: purpose, recovery scenario, billing/expiry caveat, source scope, full return payload breakdown, and cost note. It is front-loaded with the primary action and structured logically from simplest use case to detailed output semantics.

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?

For a tool that lists recent generations, the description is remarkably complete. It covers cost, ordering (newest first), what fields are returned, how lineage can be reused via create_reference, and the fact that the promptJSON enables reproduction. The presence of an output schema further reduces the burden, but this description would be nearly sufficient even without it.

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?

The single parameter 'limit' is fully described in the input schema (default 5, no ceiling, read total to detect truncation). Since schema coverage is 100%, the description does not need to add parameter detail, and it correctly focuses on output rather than repeating the schema. Baseline 3 is appropriate.

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+resource: 'List your recent successful generations and return their download URLs again.' It immediately distinguishes itself from siblings like generate_image_set by focusing on retrieval/recovery rather than creation, and even names the recovery use case explicitly.

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?

It states exactly when to use this tool: 'Use this to recover a generation whose result message was lost (for example a dropped connection mid-call).' It also gives important context about billing and expiry, and mentions that generations from the logospell.com page appear here too, helping an agent decide when this is the right call.

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.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct role: generation is split by output type (single illustration vs. solid-color set vs. transparent set), and the remaining tools handle references, delivery editing, icon export, credit checking, and listing. The three generation tools are heavily cross-referenced with explicit guidance on when to use each, leaving no boundary ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (check_credits, create_reference, edit_image_set, export_icons, generate_illustration, list_recent_generations). The two set-generation variants differ by a descriptive adjective but still follow the same generate_*_set shape, so the naming pattern remains predictable.

Tool Count5/5

Eight tools is well-scoped for an image generation service: three generation variants, one reference-upload helper, one delivery editor, one export tool, one credit checker, and one history/retrieval tool. Each tool serves a distinct workflow step without unnecessary redundancy.

Completeness4/5

The core lifecycle is well covered: generate (all three modes), upload references, edit delivered sets, export icons, check credits, and retrieve past generations. The only notable gap is that illustrations cannot be edited or re-delivered after generation, though the tool descriptions make this an explicit design constraint rather than an oversight.

Resources