Skip to main content
Glama

Create GIF or short video

create_gif_or_short_video

Generates a short animation from a text prompt, with GIF, MP4 or WebM output. Costs 50 credits. Starts a background job; returns a project id for wait_for_image_project. Before choosing settings, read get_account_info and the current parameter constraints. A listed model, resolution, duration or count is not necessarily available together or on this account. Preserve explicit requirements and all supplied inputs; explain a genuine block instead of submitting an incompatible request. Account balance alone does not prove a request is affordable.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "style": "<style>"
    },
    "name": "create_gif_or_short_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional project name for identifying this output. Omit to use the API's default project name.Ai Gif - dateTime
styleYesText instructions for the animation's subject, appearance and motion.
output_formatNoThe output file format for the generated animation.gif

Output Schema

NameRequiredDescriptionDefault
idYesUnique ID of the image. Use it with the [Get image Project API](https://docs.magichour.ai/api-reference/image-projects/get-image-details) to fetch status and downloads.
credits_chargedYesThe amount of credits deducted from your account to generate the image. We charge credits right when the request is made. If an error occurred while generating the image(s), credits will be refunded and this field will be updated to include the refund.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / style / properties / prompt / maxLength
      Previous value: -500New value: +4000
  2. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Give your gif a custom name for easy identification."New value: +"Optional project name for identifying this output. Omit to use the API's default project name."
    • addedInput schema / properties / style / description
      Added value: +"Text instructions for the animation's subject, appearance and motion."
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Strongly adds behavior beyond annotations: the 50-credit cost, that it starts a background job, and that it returns a project id consumed by wait_for_image_project. That is genuinely useful async and cost context. However, it then warns about "model, resolution, duration or count" availability, none of which exist as parameters on this tool, so part of the disclosure is generic boilerplate rather than tool-specific behavior.

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?

Front-loaded with purpose, cost, and the async pattern, then the constraint caveats. The last three sentences about availability, preserving inputs, and balance are generic policy text that reads as boilerplate, slightly diluting the tool-specific content.

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?

An output schema exists, so return-value explanation is not required, and the async/cost note is the key missing context an agent would need, which it supplies. The completeness is undermined by referencing availability of model, resolution, duration and count parameters that this schema does not define, and by never clarifying how this differs from create_video_from_text.

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% and the nested style.prompt is fully documented in the schema, so the baseline is 3. The description adds the output format choice, which the enum already conveys, while the availability caveat refers to parameters this tool does not have, so it contributes no real meaning about name, style, or output_format.

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?

"Generates a short animation from a text prompt, with GIF, MP4 or WebM output" is a specific verb plus resource with the output formats named, so an agent knows exactly what is produced. It does not explicitly distinguish itself from near-siblings like create_video_from_text or create_animation, leaving the boundary to inference.

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?

Gives real preconditions: read get_account_info and current parameter constraints before choosing settings, and it names wait_for_image_project as the follow-up call. It also tells the agent how to behave when a request is blocked. What it lacks is an explicit statement of when to pick this over create_video_from_text or create_animation.

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.