Skip to main content
Glama

PrismPoster Studio

by com.prismposter
OverviewDiscussionsAdmin

Extend a video

extend_video

Make a clip longer: continue the same scene from its last frames for a few more seconds, carrying on naturally or doing what you describe next. Priced on the added seconds only. Returns the longer clip; the original is kept. Spends the account's PrismPoster credits at the same price as on prismposter.com (quote_job prices it first, free). When the person must decide something first (a price above their ask-first amount, consent for real people in pictures, the right to use a clip), it returns approval_required and nothing runs until they answer in PrismPoster's card or at the link. Everything made is saved to their PrismPoster library. Requests involving anyone under 18 or depicting public figures or office holders are refused before any charge.

Input Schema

NameRequiredDescriptionDefault
engineNoDefaults to the engine the clip was made with.
clip_idNoThe clip to work on: one PrismPoster made, as a clip_id from get_job or a video asset_id from list_library.
directionNoOptional: what happens next. Leave it out to carry the scene on naturally from the last frames.
resolutionNoDefaults to the clip's own.
add_secondsNoHow many seconds to add to the end: 4, 6, 8, 10 on the standard engine, 4-30 on premium.
approval_idNoOnly after an approval_required answer: the approval_id it returned, once the person has answered. The job then runs exactly as they approved it and the other arguments are ignored.
idempotency_keyNoOptional. A unique key for this job (8-128 letters, digits, . _ : -). Repeating a call with the same key returns the first call's job instead of starting and charging a second one, so set it whenever a retry is possible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: billing is on added seconds only, credits are spent at quoted prices, original clip is preserved, output lands in the user's library, and approval_required blocks execution until the person answers. Content refusals for minors and public figures are disclosed before any charge, which the idempotentHint/destructiveHint fields say nothing about.

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?

Purpose is front-loaded in the first clause and each sentence carries distinct information (behavior, pricing, approval, policy). It is dense but slightly overloaded near the end with refund/policy detail in a single long run-on.

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?

For a 7-parameter, zero-required, credit-spending mutation with no output schema, the description supplies what's missing: what is returned (longer clip), what happens to the original, how charging works, and the approval/resume path.

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 engine, resolution, direction and add_seconds are already fully documented. The description only reinforces that pricing scales with added seconds; it adds no format or constraint detail the schema lacks, so baseline 3 applies.

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?

States a specific verb and resource plus mechanism: 'continue the same scene from its last frames for a few more seconds.' That distinguishes it from create_video (new clip), change_video and upscale_video without the agent needing the schema.

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

Usage Guidelines4/5

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

Says when to use it (make an existing clip longer) and routes to quote_job for a free price first, plus the approval_required branch. It does not explicitly exclude sibling alternatives like change_video or remake_render, so sibling differentiation is only partial.

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

All PrismPoster Studio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources