Skip to main content
Glama

Media Forge: AI Image & Video Generator - ManyMotions

Update Media Forge Project

update_media_forge_project
Idempotent

Update the prepared Media Forge project with edited widget settings before opening ManyMotions or generating. Intended for the widget UI. 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": {
      "project_id": "<project_id>"
    },
    "name": "update_media_forge_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNo
countNo
ratioNo
promptNo
durationNo
model_idNo
model_nameNo
project_idYes
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=true, openWorld=false, so the safety profile is covered. The description adds real behavioral context the annotations do not: it is a pre-generation settings edit bound to the widget UI, not a media creation or conversion step. It does not clarify partial-update semantics (whether unspecified parameters are preserved or reset), which is the remaining gap.

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, front-loaded with the action and the workflow position before the exclusions. The exclusion list is long but each item rules out a plausible but wrong invocation, so it earns its space.

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 no explanation, and annotations carry the safety profile. However, for a 10-parameter, 0%-documented update tool, the description leaves the meaning and format of its inputs entirely unaddressed, which is a meaningful completeness gap.

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 10 parameters, including ambiguous ones like model_id vs model_name, ratio, resolution, duration (integer or string) and an open advanced_params object. The description only hints at 'widget settings' and prompt type; it explains none of these fields, so the agent must guess formats and which are optional beyond project_id.

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?

The description names a specific verb and resource ('Update the prepared Media Forge project with edited widget settings') and situates it in the workflow ('before opening ManyMotions or generating'). That positioning alone distinguishes it from prepare_media_forge_project and generate_media_forge.

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?

Explicit when-to-use ('only for text-to-image or text-to-video prompts', 'Intended for the widget UI') plus an extensive when-not list covering uploaded/reference images, editing, background replacement, image-to-video, video-to-video, remixing and upscaling. This is as close to a routing rule as a description gets.

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