Skip to main content
Glama

Create jobs and their results

list_creations
Read-onlyIdempotent

Status and result links of Create jobs (images, videos, angles, talking photos, brand films, reframes, cut-outs, motion copies, breakdowns, character portraits). Pass job_id for one job. status: queued, rendering, done or error (a failed job refunds its credits). Free.

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

Input Schema

NameRequiredDescriptionDefault
toolNoOnly this tool's jobs
limitNo
job_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 safety is covered. The description adds genuinely useful non-annotation behavior: a failed job refunds its credits, and the call is free. It does not describe pagination behavior (limit caps at 50) or the shape of the returned result links.

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?

Three short sentences plus a parenthetical, front-loaded with the purpose and status life cycle. The long job-type parenthesis is dense but each item disambiguates scope, so little is wasted; only the trailing "Free." feels appended.

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

Completeness3/5

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

With no output schema, the description should explain return shape but only says "status and result links", leaving the agent unsure what fields come back. Missing limit semantics and any polling recommendation leaves gaps for a 3-param listing tool, though annotations cover safety adequately.

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 coverage is only 33%, so the description must compensate. It does explain job_id (single-job lookup) and enumerates the job kinds that map onto the `tool` enum, but it never mentions the `limit` parameter or its 1-50 range/default of 10, 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.

Purpose4/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 (status and result links of Create jobs) and enumerates the job types covered (images, videos, angles, talking photos, brand films, etc.). It is clearly a read/listing tool for generation jobs, distinguishable from creation siblings, though the parenthetical type list blurs the line against list_clips/list_characters rather than explicitly ruling them out.

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?

"Pass job_id for one job" gives one concrete usage cue, and the status enumeration hints at polling use. However, it never states when to use this versus list_clips, list_characters, list_photo_sets or list_carousels, nor when to poll versus wait, so routing relies on 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.