Skip to main content
Glama

Animate image

animate_image

Turn a finished image into a short video with an image-to-video model. SPENDS CREDITS unless mock or estimate_only is true (estimate_only gives the price). The first frame is the format's crop without text. Returns a video job_token; follow with wait_for_jobs, then render_video to add captions, voiceover and music.

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

Input Schema

NameRequiredDescriptionDefault
cropNoWhere a format's window sits on the master. The focal point lands in the middle of the format's clear area (between Story UI bands on 9:16).
mockNo
modelNokling-3-std-i2v
formatNoRequired with image_url; overrides the token's format
promptNoHow it should move. The image already shows the scene.
max_usdNoThe same cap in dollars ($0.01 a credit)
asset_idNoOr one of the brand kit's own product images (get_brand lists them); needs brand_id and format
brand_idNoA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.
durationNoKling: 5 or 10. Seedance: 5, 10 or 15.
image_urlNoOr any public https image, or a stored one such as a place_screen result
job_tokenNoA completed image job_token from generate_assets (format and crop come from it)
max_creditsNoRefuse (submit nothing) if the price in credits is above this
native_audioNo
estimate_onlyNoPrice it (and cut the still) without submitting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag a non-read-only, open-world, non-idempotent write. The description adds the critical trait that is not in the annotations: each call spends credits unless mock/estimate_only is set, and it discloses the async shape (a job_token is returned, not a video). It does not cover failure/refund behavior or what happens if a job is cancelled, leaving a modest gap.

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 plus a pipeline clause, front-loaded with the action, then the cost warning, then the return value and next steps. Every sentence carries non-redundant information and the credit warning is not buried.

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?

For a 14-parameter tool with a nested crop object and no output schema, the description supplies the essentials: cost warning, what the returned token is, and the two follow-up tools. It stops short of describing job failure, polling expectations, or the cost estimate's shape, which matters given how many billing-related params exist.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 79% schema coverage the baseline is 3, and the description earns above that by giving meaning to estimate_only ('gives the price'), mock, and crop ('the first frame is the format's crop without text'). It still says nothing about max_credits refusal, duration-by-model, or native_audio beyond what the schema carries.

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 ('turn a finished image into a short video') plus the mechanism ('image-to-video model'), and implicitly distinguishes itself from render_video by reserving captions/voiceover/music for that step. An agent can tell what this produces without opening the schema.

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?

Explains the cost condition (credits unless mock or estimate_only) and gives an explicit follow-on chain: wait_for_jobs then render_video for captions and music. It does not state prerequisites for obtaining the input image (generate_assets is only referenced via the job_token param) or when to pick this over a plain render, so it stops short of full routing.

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