PrismPoster Studio

Cut a clip for every placement

create_placement_set

Turn one finished clip into ready-to-post cuts for each placement (Instagram Reels, TikTok, YouTube Shorts, Facebook Reels, Instagram feed 4:5 and square, YouTube 16:9), cropped to fill each frame, with an optional caption placed inside each platform’s safe area so its buttons and text never cover it. Make or pick the clip first (create_video, list_library). Priced like an export from the editor, per cut. The tallest cut is also saved as an editor project. 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

Name	Required	Description	Default
`caption`	No	Optional words burned onto every cut (a hook, an offer, a product name), at most 90 characters. Placed inside each platform’s safe area, clear of its buttons and text.
`clip_id`	No	The clip to cut: a clip_id from get_job, a video asset_id from list_library, or the asset_id import_media returned for the person's own MP4 or MOV.
`placements`	No	Where it will run. Defaults to instagram-reels, tiktok, youtube-shorts, instagram-feed-portrait.
`approval_id`	No	Only 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_key`	No	Optional. 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.
`caption_position`	No	Where the caption sits inside the safe area.	bottom

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing credit spend, per-cut export-equivalent pricing, free quote preflight, approval_required gating, saved library outputs, and the editor-project side effect for the tallest cut. The opt-in idempotency_key also adds retry behavior without contradicting idempotentHint=false.

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?

The purpose is front-loaded and the description is structured around what it does, prerequisites, pricing, approval, and refusals. It is somewhat long, with a few side-effect sentences that could be compressed, but the length is largely justified by billing and approval complexity.

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

Completeness4/5

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

Covers prerequisites, cost, approval flow, refusal rules, and where outputs are saved, which is substantial for a complex mutation tool. However, without an output schema, it does not explain what a normal successful response contains, such as job identifiers or cut references.

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 parameters are already well-documented. The description repeats caption safe-area placement, clip sources, and placement defaults, but adds little syntax or meaning beyond the schema itself.

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: turning one finished clip into placement-specific cuts, with cropping and optional captions. It enumerates placements and distinguishes prerequisite siblings like create_video and list_library, so the agent can identify the tool's role immediately.

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?

Explicitly says to make or pick the clip first via create_video or list_library, to use quote_job for free pre-pricing, and that approval_required pauses execution until the person answers. It also states hard refusal cases for minors, public figures, and office holders, giving clear when-to-use and when-not-to-use guidance.

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

All PrismPoster Studio tools Inspect

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

Need Help?