io.github.Headdao/slidemaster-mcp

batch_generate_scripts

Generate narration scripts for every slide in a project with a single batch request. Provide a project ID, choose a script style, and optionally target specific slides or force regeneration.

Instructions

Generate narration scripts for ALL slides in a project in one batch operation.

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": "batch_generate_scripts"
  }
}

Input Schema

Name	Required	Description
`slide_ids`	No	Optional subset of slide IDs to generate scripts for; omit for all slides
`project_id`	Yes	Project ID to generate scripts for
`regenerate`	No	Force regeneration even if scripts already exist (default: false)
`prompt_style`	No	Script style applied to all slides, e.g. 'professional', 'casual', 'educational'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Sep 6, 2026

TDQS

B3.4/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 burden of behavioral disclosure. It does not mention whether existing scripts are overwritten, whether the operation is asynchronous, whether partial failures can occur, or what side effects the batch operation has. The schema's regenerate parameter hints at overwrite behavior, but the description itself is silent on it.

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 description is a single, front-loaded sentence with no wasted words. It quickly communicates the core action and scope, making it easy for an agent to parse.

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

Completeness2/5

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

For a batch operation with no annotations and no output schema, this description is too thin. It omits important operational context such as return behavior, async/sync execution, whether the project must already contain slides, and what happens when some slides already have scripts.

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 the schema already documents all four parameters. The description adds the batch/all-slides framing but does not clarify the optional slide_ids subset, and it does not provide meaningful semantic detail beyond what the schema already states.

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 states a specific action ('Generate narration scripts'), a clear resource ('ALL slides in a project'), and a distinguishing mode ('one batch operation'). This makes it easy to differentiate from the sibling generate_script tool, which presumably handles a single slide.

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

Usage Guidelines3/5

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

The phrase 'ALL slides in a project in one batch operation' implies the tool is for bulk script generation rather than per-slide generation. However, it does not explicitly name the alternative (generate_script) or state when not to use this tool, so usage guidance remains mostly implied.

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