picorn_video_render_projectRender the native timeline to a finished MP4/H.264 or WebM/VP9 file. The render includes multi-slide sequencing, timed layers, video frames, keyframe animation and mixed audio, and returns a public video URL plus /video/editor link.
| Name | Required | Description | Default |
|---|---|---|---|
| fps | No | ||
| format | No | ||
| quality | No | ||
| slideIds | No | ||
| projectId | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With annotations only providing readOnlyHint=false and openWorldHint=true, the description adds some behavioral context: it lists what the render includes (multi-slide sequencing, timed layers, video frames, keyframe animation, mixed audio) and what it returns (a public video URL plus /video/editor link). However, it does not disclose potential side effects, whether the operation is asynchronous, cost/resource implications, or error behaviors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core action and output format. The second sentence efficiently bundles inclusions and return values. No filler or redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a render operation with 5 parameters and no output schema, the description provides a solid overview of inputs (projectId implied), what happens during rendering, and the output. However, it omits parameter-specific details (e.g., fps, quality), usage guidance, and potential blocking/async behavior, leaving gaps for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% (no property descriptions), so the description must compensate. It partially explains the `format` param via 'MP4/H.264 or WebM/VP9' and `slideIds` via 'multi-slide sequencing', but it does not attribute meaning to `fps` or `quality`. The description adds some value but is insufficient for the full parameter set.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Render the native timeline to a finished MP4/H.264 or WebM/VP9 file.' It specifies a verb ('Render'), a resource ('native timeline'), and output formats. However, it does not explicitly differentiate from the sibling tool 'picorn_editor_render_project', leaving the distinction to names/titles rather than the description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (for rendering a video project to a finished file) but does not provide explicit when-not guidance or mention alternatives. It lacks prerequisites, constraints, or comparisons to other render-related sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or operation, with clear boundaries between image generation/editing and the many editor/video actions. Descriptions further clarify any potential overlap, making misselection unlikely.
Most tools follow a verb_noun pattern, but the projects_* tools (create, inspect, update) reverse to noun_verb, and capabilities is a bare noun. This mixed convention is readable but not fully consistent.
With 30 tools, the set exceeds the 25-tool threshold and feels heavy for an MCP server. While the broad scope justifies some size, many tools could be consolidated or split into focused servers.
Core image, editor, and video workflows are covered, but there are notable gaps such as no delete operations for editor/video projects, no update for video projects, and no lifecycle management for imported assets. These missing operations can create dead ends.