Skip to main content
Glama

Retry a prepared film assembly

playground_film_assembly_retry

After two failed assembly attempts, validate the ordered Playground clips and queue another bounded FFmpeg assembly attempt. This does not submit a paid media generation job.

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": {
      "projectId": "<projectId>",
      "runId": "<runId>"
    },
    "name": "playground_film_assembly_retry"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID returned by preparation or execution for this project.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
runIdYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The description adds significant behavioral context beyond the annotations, such as mentioning 'bounded FFmpeg assembly attempt' (an implementation detail/constraint) and clarifying it doesn't submit a paid job. While annotations cover safety, the description provides critical operational limits.

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?

The definition is highly concise. Both sentences are packed with necessary, non-redundant information, and the most vital behavioral constraint (the retry context) is stated first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the detailed input schema and annotations, the description covers all critical operational context for the agent, including failure modes and process boundaries. No major gaps exist for correct invocation.

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?

Since the schema coverage is 100%, the description does not need to elaborate on the parameters 'projectId' or 'runId.' The description adds no meaningful semantic value beyond the structure already provided.

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 clearly states the function is to retry a prepared film assembly, specifically detailing the internal process (validating ordered clips and queuing a bounded FFmpeg attempt). This leaves no ambiguity about what the tool accomplishes.

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?

Usage is bounded by a specific condition: it should only be used after two failed assembly attempts. It also provides a critical exclusion ('does not submit a paid media generation job'), which is essential guidance for correct tool selection.

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.