Skip to main content
Glama

Use a Remix template as the driving video

swap_import_template
Idempotent

Copy a Remix template's clip (an id from browse_templates {source:"remix"}) into the user's swap uploads and return it as a driving video for create_character_swap: drivingVideoR2Key, drivingVideoFileName, drivingDurationSeconds, plus the template's prompt. Pair it with a character image from swap_import_character or swap_upload and call create_character_swap with engine "pro". FREE: nothing is generated here.

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": {
      "templateId": "<templateId>"
    },
    "name": "swap_import_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYesA template id from browse_templates {source:"remix"}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare a non-read-only, idempotent, non-destructive write, so the copy semantics are largely covered. The description does add real value beyond them: the "FREE: nothing is generated here" cost note and the explicit set of returned fields (drivingVideoR2Key, drivingVideoFileName, drivingDurationSeconds, prompt). It does not say what error conditions or file limits apply, but that is a minor gap given the annotation coverage.

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?

Heavily front-loaded: what is copied and what comes back appear in the first sentence, with the workflow pairing and cost note following. It is dense rather than padded, though the inline enumeration of three camelCase return keys makes the first sentence slightly hard to scan.

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?

There is no output schema, so the description usefully enumerates the returned fields, and it supplies the full call sequence plus the cost model for a one-parameter tool. Nothing essential to invoking it correctly is absent, though guidance on invalid or stale template ids would round it out.

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% and the single templateId parameter is documented in the schema with the same browse_templates {source:"remix"} provenance. The description merely repeats that constraint rather than adding format, validation, or failure-mode detail, so the baseline 3 applies.

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 concrete verb and resource — copying a Remix template's clip into the user's swap uploads — and specifies the exact outcome (a driving video for create_character_swap, listing the returned keys). It is clearly distinguishable from browse_templates (which supplies the id) and from swap_import_character / swap_upload (which supply the character image).

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 routes the agent: obtain a templateId from browse_templates {source:"remix"}, pair this result with an image from swap_import_character or swap_upload, then call create_character_swap with engine "pro". What's missing is any when-not guidance (e.g. what to do if the user already has a driving video, or when to prefer swap_upload instead).

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