Media Forge: AI Image & Video Generator - 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_media_forge_project 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

Name	Required	Description	Default
`project_id`	Yes

Output Schema

Name	Required	Description	Default
`job`	No
`state`	No
`balance`	No
`message`	No
`project`	Yes
`dashboard_url`	Yes
`credits_required`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds real side-effect semantics beyond the annotations: the refresh can save completed media or refund credits on a failed job. That is consistent with readOnlyHint=false, destructiveHint=false, and idempotentHint=true, and it tells the agent what actually happens on invocation. No auth or rate-limit context, but the return shape is covered by the output schema.

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, front-loaded with the action, then side effects, then prerequisite. Every sentence carries information and none repeats schema or annotations.

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?

Complete enough given the output schema covers return values and the annotations cover the safety profile: the description states the prerequisite, the side effects, and the boundary against new generation. Only the identity of project_id is left implicit.

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 project_id is undocumented in the schema. The phrase 'for a prepared project' hints that project_id is the prepared project's id, but the description never states it, so it only partially compensates for the coverage gap.

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?

Names a concrete verb (Render) and resource (inline Media Forge widget) and scopes it to 'a prepared project'. It also states that it refreshes an existing generation job and 'never starts a new generation', which implicitly separates it from generate_media_forge, though it stops short of naming that sibling explicitly.

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_media_forge_project first') and an implicit exclusion ('it never starts a new generation'), so an agent knows not to reach for this to kick off work. It lacks an explicit 'use X instead' pointer for the start-a-generation case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Media Forge: AI Image & Video Generator - ManyMotions tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?