Skip to main content
Glama

Singing Pet

Create a singing pet video

create_singing_video

Animate a pet photo so the pet appears to sing a song, with the mouth synced to the audio. Takes a public URL to a photo (one pet, facing the camera, well lit works best) and a template_id from list_song_templates. Costs 1 credit. Rendering takes about a minute, so this returns immediately with a video id - poll get_video_status until it is completed.

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": {
      "image_url": "<image_url>",
      "template_id": "<template_id>"
    },
    "name": "create_singing_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_urlYesPublic HTTPS URL to a photo of the pet. JPEG, PNG, WebP or HEIC, up to 15MB.
template_idYesSong to sing, from list_song_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive and non-open-world, and the description adds substantial context on top: a 1-credit cost, ~1 minute async render, and an immediate return of a video id rather than the finished asset. That said, nothing is said about what happens on failure or whether a failed render still consumes the credit, which matters for a costly async mutation.

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 dense sentences, front-loaded with the action and followed by input requirements, cost, and async follow-up. Nothing is redundant with the schema fields and no sentence is wasted.

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?

Although there is no output schema, the description compensates by naming the return value (a video id) and the polling tool that consumes it, and it covers cost and latency. That is everything an agent needs to invoke and follow through correctly.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds real guidance beyond the schema by stating the image should contain one pet, face the camera, and be well lit. The template_id semantics are only restated from the schema.

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 ('Animate a pet photo so the pet appears to sing a song') plus the mechanism (mouth synced to audio), which distinguishes it from the sibling create_pet_song without needing schema inspection.

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 clear operational context: template_id must come from list_song_templates, and the result must be polled via get_video_status until completed. It doesn't explicitly say when to prefer this over create_pet_song, so the sibling-exclusion guidance is implicit rather than stated.

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