Skip to main content
Glama

Cast swap

cast_swap

Replace the people in a 4–30 s clip with the people in your photos. subjects: [{photos: [file ids], kind?: person|object, label?, slot?: left|center|right|main, placement?}], up to 4 subjects / 9 photos.

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": {
      "source_video_file": "<source_video_file>",
      "subjects": "<subjects>"
    },
    "name": "cast_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
subjectsYes
resolutionNo720p
confirm_creditsNo
source_video_fileYes
keep_original_soundNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's added value here is the operational limits: 4-30 s source, up to 4 subjects, 9 photos total. It says nothing about cost, credit consumption (despite a confirm_credits parameter), or that the job is asynchronous and must be polled, which are the behaviors that actually matter for this mutation.

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?

Two sentences, both earning their place: the core operation is front-loaded, then the subject shape and caps follow. The inline pseudo-schema notation is dense and slightly cryptic, but it is not wasted wording.

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 values need not be described. Still, for a six-parameter generative mutation with no schema descriptions, the definition leaves credit confirmation, output resolution, and audio-retention behavior unaddressed, which leaves real gaps for correct invocation.

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 0%, so the description carries the burden, and it does document the hardest parameter well: subjects' photos, optional kind enum, label, slot positioning, placement, plus the 4-subject/9-photo caps. However, source_video_file, resolution, keep_original_sound, notes and confirm_credits get no explanation at all, so compensation is only partial.

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?

States a concrete verb and resource: replace the people in a short clip with people from supplied photos, plus the duration bound (4-30 s). That is enough to separate it from siblings like lipsync or talking_head_video, though it never names or contrasts those alternatives explicitly.

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?

Usage is implied by the clip-length constraint and the photo-subject model, so an agent can infer this is the tool for swapping casts in an existing video. There is no explicit when-to-use/when-not guidance, no mention of prerequisites such as having uploaded photos, and no pointer to estimate_cost or wait_for_generation for the generation lifecycle.

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