ClipFlux

Show a post before it goes out

prepare_post

Read-only

Shows the ClipFlux post card for a made video: the YouTube channel, the description, when it goes out, who can see it (public, unlisted or private) and whether it is made for kids. Posts nothing. Call it when the user wants to post or schedule, then wait for their yes before post_video. The YouTube title is written from the script when it posts; do not ask for one. Ask the user whether the video is aimed at kids (YouTube calls it "made for kids": made mainly for children, not just fine for them to watch); never decide it for them.

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": {
      "videoId": "<videoId>"
    },
    "name": "prepare_post"
  }
}

Input Schema

Name	Required	Description
`when`	No	"now", "after_export" (as soon as the export is done), or a date and time as ISO 8601 with the user's time zone, for example "2026-10-28T18:00:00+01:00". Default "now".
`privacy`	No	Who can see this video on YouTube, if the user said: public, unlisted (only people with the link) or private (only them). Leave it out to use the channel's default.
`videoId`	Yes	The video id, from draft_video, list_my_videos or get_video.
`accountId`	No	The channel id from list_accounts, if the user named one.
`description`	No	The YouTube description, if the user wants one. Leave it out and ClipFlux writes one from the video.
`madeForKids`	No	The user's answer to "is it made for kids?". Leave it out until they have answered.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Posts nothing'. It adds real value beyond the annotations by disclosing the confirmation gate before post_video and the fact that the YouTube title is derived from the script at post time, though it does not describe the shape of the returned card beyond naming its fields.

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?

Five short sentences, front-loaded with what is shown and the reassurance that nothing is posted, followed by the flow rule and the two prohibitions. No filler and nothing repeated from the schema verbatim.

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 six-parameter preview tool with full schema coverage and no output schema, the description supplies everything an agent needs: what it displays, that it is side-effect free, the hand-off order to post_video, and how to handle the ambiguous kids flag. No material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage the baseline is 3, and the description earns above that by clarifying the trickiest parameter: it spells out that 'made for kids' means made mainly for children, 'not just fine for them to watch', which the schema does not. It also explains that the title is auto-generated so no title parameter is needed or should be requested.

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 ('Shows the ClipFlux post card for a made video') and enumerates the fields displayed: channel, description, publish time, visibility, made-for-kids. It also explicitly negates the write behavior ('Posts nothing'), which cleanly separates it from the sibling post_video.

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?

Gives an explicit trigger ('when the user wants to post or schedule'), an explicit sequencing rule ('then wait for their yes before post_video'), and two explicit don'ts ('do not ask for' a title, 'never decide' the kids setting for them). Alternatives and preconditions are both named.

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

All ClipFlux 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?