Skip to main content
Glama

Kubeez

get_generations

Read-onlyIdempotent

Scope: read:generations. Return the user's media-generation history, newest first — covers BOTH the current session's jobs (still queued / processing / just-completed) AND prior sessions. Each row includes id, prompt, model, generation_type, status, created_at, completed_at, processing_time_ms, credits_deducted, error_message, and an outputs[] array with the playable/viewable URL(s), thumbnails, dimensions, duration, format, and file size — enough to render a gallery without a follow-up call. limit is 1–25 (default 25; higher values are clamped). Optional filters: status, model (model_id), generation_type (text-to-image, image-to-video, etc.). Use this when the user asks 'what have I made', 'show me my last 10 videos', or to surface re-usable assets. For a single generation's full live status (poll until done), use get_status(id).

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": "get_generations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
modelNo
statusNo
generation_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real context on top: ordering (newest first), that queued and in-flight jobs appear alongside finished ones, and that limit values above 25 are silently clamped rather than erroring. The one gap is that there is no offset/cursor, so history beyond 25 rows is unreachable and the description never says so — an agent could over-promise a complete history.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Scope prefix and core behavior are front-loaded, and the when-to-use routing sentence closes it well. The long enumeration of every returned row field is partly redundant given an output schema exists, though it does support the useful claim that a gallery can be rendered without a follow-up call.

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 filtered read-only list tool with annotations covering the safety profile and an output schema covering return shape, this description supplies everything else an agent needs: ordering, session coverage, limit bounds and clamping, filter set, and a sibling routing rule.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 the load and largely does: limit is bounded 1–25 with default 25 and clamping behavior, model is identified as a model_id, generation_type is illustrated with enum-ish examples (text-to-image, image-to-video), and status is named as a filter. The only unexplained detail is that the empty-string defaults mean 'no filter', which is minor.

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 ("Return the user's media-generation history, newest first") plus scope (current session jobs AND prior sessions). It explicitly distinguishes itself from get_status(id) for single-generation live polling, so an agent can route between the two without opening either 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 concrete trigger utterances ("what have I made", "show me my last 10 videos") and a stated use case (surface re-usable assets). It also names the alternative — get_status(id) for polling one generation to completion — and the condition that selects it.

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