Skip to main content
Glama

Check an image or video

get_creation
Read-onlyIdempotent

Check images or videos started with create_image or create_video: status, minutes left, and the finished link when ready. With wait true the call waits up to 40 seconds for them to finish, so you can wait for the result in the same answer and then give the user the link.

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

Input Schema

NameRequiredDescriptionDefault
idNoOne id (instead of ids)
idsNoIds from create_image or create_video, e.g. 'vid_...'
waitNoWait up to 40 seconds for them to finish. Default false.

Output Schema

NameRequiredDescriptionDefault
creationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / creations / items / properties / saveUrl
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the bar is lower; the description still adds the genuinely useful block-until-ready semantics with a bounded 40-second wait. It omits what is returned if the wait expires or whether the wait blocks the agent's other work.

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?

Two sentences, zero padding, with the identification of valid inputs front-loaded ahead of the waiting behavior. Every clause carries information an agent needs.

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 no prose, and the description adequately covers polling and the wait workflow. The one gap is post-timeout behavior — whether the call returns a pending status plus minutes remaining or errors.

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 100%, so the schema already documents id, ids, and wait. The description only reinforces the wait flag with a rationale (same-answer workflow) and says nothing to disambiguate single id versus the up-to-4 ids list beyond what the schema states.

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 ('check images or videos started with create_image or create_video') and enumerates what comes back: status, minutes left, finished link. The origin-tool scoping cleanly separates it from siblings like list_creations and the create_* tools.

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

Usage Guidelines4/5

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

Explicitly gates use to creations from create_image/create_video and explains when to set wait=true ('so you can wait for the result in the same answer'). It stops short of naming the alternative for browsing creations (list_creations) or saying when not to poll this way.

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