Skip to main content
Glama

Media Forge: AI Image & Video Generator - ManyMotions

Prepare Media Forge Project

prepare_media_forge_project

Prepare a ManyMotions Media Forge image or video generation project from a prompt and visible settings. Call this immediately whenever the user describes an image or video they want — do not ask clarifying questions first; infer sensible settings from the request and let the user adjust them in the widget. This renders the review/generation widget immediately and does not consume credits. No sign-in is needed to prepare. Use this only for text-to-image or text-to-video prompts. Do not use it for uploaded/attached/provided/reference images, image editing, background replacement on an existing image, product-photo editing, image-to-video, video-to-video, remixing, upscaling, or other media-to-media workflows.

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": {
      "tab": "<tab>",
      "prompt": "<prompt>"
    },
    "name": "prepare_media_forge_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYes
countNo
ratioNo
promptYes
durationNo
model_idNo
model_nameNo
resolutionNo
advanced_paramsNo

Output Schema

NameRequiredDescriptionDefault
jobNo
stateNo
balanceNo
messageNo
projectYes
dashboard_urlYes
credits_requiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations mark this as a non-read-only, non-idempotent, non-destructive, closed-world operation, so the safety bar is partly covered. The description adds genuinely useful context the annotations cannot: it renders the review/generation widget immediately, does not consume credits, and needs no sign-in. It stops short of saying what state is persisted or how the prepared project is later consumed.

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?

Front-loaded with the core action and the call-immediately directive, then a long but high-value exclusion list. The 'call this immediately' and 'do not ask clarifying questions first' clauses overlap slightly, but nothing else is filler.

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?

For a 9-parameter, nested-object tool the workflow guidance is strong and an output schema exists so return values need no explanation. The gap is that none of the generation-shaping parameters (tab, ratio, duration, model, resolution, count, advanced_params) are documented anywhere, leaving the agent to guess at their meaning.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters (tab, count, ratio, prompt, duration, model_id, model_name, resolution, advanced_params), so the description must carry the burden and largely does not. Only 'prompt' and a vague reference to 'visible settings' / 'infer sensible settings' are touched; tab, count limits, ratio strings, duration enum values, model selection and advanced_params semantics are never explained.

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?

The description gives a specific verb+resource: 'Prepare a ManyMotions Media Forge image or video generation project from a prompt and visible settings.' It also pins the scope to text-to-image/text-to-video only. It never names its siblings (generate_media_forge, render_media_forge_widget, update_media_forge_project), so the boundary against those is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to call it ('Call this immediately whenever the user describes an image or video'), how to call it ('do not ask clarifying questions first; infer sensible settings'), and an unusually complete when-not list covering uploads, editing, background replacement, product-photo editing, image-to-video, video-to-video, remixing and upscaling.

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