PhotoForge MCP Server

generate_production_script

Generates a full commercial video production script and storyboard sequence from your concept, target audience, and duration.

Instructions

Generate a full commercial video production script and storyboard sequence.

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": {
      "concept": "<concept>"
    },
    "name": "generate_production_script"
  }
}

Input Schema

Name	Required	Description
`concept`	Yes	Campaign or video concept.
`targetAudience`	No	Target audience and platform.
`durationSeconds`	No	Total duration in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about credit consumption, whether generation is synchronous or long-running, or what form the 'storyboard sequence' takes (text, images, both). For a generative tool in a suite that tracks remaining_credits, this is a meaningful 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?

A single well-formed sentence with no waste and the deliverable front-loaded. It is efficient, though its brevity is part of the transparency shortfall rather than a virtue in itself.

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?

With no output schema and no annotations, the description should clarify the return shape and cost implications of a generation call. It confirms the two artifacts produced but leaves format, length expectations, and consumption behavior unstated.

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 100%, so all three parameters are already documented, establishing the baseline of 3. The description adds no extra meaning such as valid duration ranges or how targetAudience influences the script.

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?

Specific verb ('Generate') plus a concrete dual deliverable ('production script and storyboard sequence'), scoped to commercial video. It clearly differs from siblings like generate_video or generate_caption, though it never explicitly names those alternatives.

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

Usage Guidelines2/5

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

No indication of when to use this versus generate_video or generate_caption, no prerequisites, and no exclusions. The agent must infer the appropriate context from the name alone.

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