Skip to main content
Glama
Sign In

Framevine

by com.framevine
OverviewDiscussionsAdmin

List recent generations

list_recent_generations
Read-onlyIdempotent

List the user's most recently completed generations (images and videos) across all threads, newest first. Each item has its node id, thread id, type, operation, prompt, model, output file id, media URL and dimensions. Use the node id and thread id with get_thread or edit tools. Small preview images of the first few results are attached (videos show their poster frame).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of generations to return (default 20).
includePreviewsNoAttach preview images of the first 3 results, in order (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond annotations: scope across all threads, newest-first ordering, completed-only filtering, returned item fields, and preview attachment behavior including video poster frames. It lacks pagination or rate-limit details, so it is not exhaustive.

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 sentences, front-loaded with the tool's purpose, followed by output shape and relevant follow-up behavior. It avoids merely restating the tool name or title and every sentence contributes useful information.

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 read-only list tool with no output schema, the description supplies the return fields, ordering, scope, and preview behavior needed to invoke and interpret results correctly. Annotations cover the safety profile, and no critical contextual gap remains.

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% for both parameters, including the limit default/maximum and the preview rule for the first 3 results. The description reinforces preview behavior but does not add parameter syntax or semantics beyond what the schema already provides, so the baseline 3 applies.

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, 'List', and resource, 'most recently completed generations (images and videos) across all threads', with ordering 'newest first'. This separates it from sibling list_threads and get_generation_status by focusing on completed outputs rather than threads or in-progress status.

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 follow-up guidance, 'Use the node id and thread id with get_thread or edit tools', and implies use for recent completed outputs. However, it does not explicitly say when to choose this tool over list_library_files or list_threads, nor does it include when-not conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Framevine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources