Skip to main content
Glama

Cinematic AI Video Maker with Camera Moves - ManyMotions

Render Media Forge Widget

render_media_forge_widget
Idempotent

Render the inline ManyMotions Media Forge widget for a prepared project and refresh its existing generation job. Refresh can save completed media or refund credits for a failed job; it never starts a new generation. Always call prepare_cinematic_video first.

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": {
      "project_id": "<project_id>"
    },
    "name": "render_media_forge_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Output Schema

NameRequiredDescriptionDefault
jobNo
stateNo
balanceNo
messageNo
projectYes
dashboard_urlYes
credits_requiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the refresh can save completed media or refund credits on failure, and it never triggers a new generation. This complements readOnlyHint=false/idempotentHint=true without contradicting them. Missing details on auth requirements or what 'render the inline widget' actually does server-side keep it from a 5.

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 tight sentences, each earning its place: action, mutation semantics, prerequisite. The key constraint (no new generation) is front-loaded and the prerequisite is last, which reads naturally.

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?

With an output schema present, return values need not be described, and the description covers the prerequisite and the save/refund outcomes. The remaining gap is the undocumented project_id, which is the only input the agent must supply.

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% and there is one required parameter (project_id) that the description never explains beyond the phrase 'a prepared project'. That phrase implies the project must be prepared via prepare_cinematic_video, but the parameter itself (format, source, whether it accepts external IDs) is left undocumented.

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 specific verb+resource ('Render the inline ManyMotions Media Forge widget') scoped to 'a prepared project', and clarifies it refreshes an existing job rather than creating one. It does not explicitly differentiate itself from get_media_forge_job or generate_media_forge, so sibling separation is only partial.

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 an explicit prerequisite ('Always call prepare_cinematic_video first') and an explicit exclusion ('it never starts a new generation'), which routes the agent away from generate_media_forge. It stops short of naming that sibling or describing when to re-invoke this tool versus polling get_media_forge_job.

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