Skip to main content
Glama
Sign In

ClipFlux

by ai.clipflux
OverviewDiscussionsAdmin

Draw thumbnail pictures

draw_thumbnails

Draws the pictures for the chosen thumbnail ideas (slots a, b, c from suggest_thumbnails), 2 credits each, about a minute. Call it only for the slots the user asked for, after saying the price. show_thumbnails shows them when done. The words go on the picture in the ClipFlux Studio's Thumbnail tab, where the user also picks the one YouTube gets.

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>",
      "slots": "<slots>"
    },
    "name": "draw_thumbnails"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotsYesWhich ideas to draw.
videoIdYesThe video id, from draft_video, list_my_videos or get_video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive, closed-world operation; the description adds cost ('2 credits each'), latency ('about a minute'), and where the output surfaces ('ClipFlux Studio's Thumbnail tab', where the user picks the YouTube one). Those are exactly the side effects an agent needs before spending credits.

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?

Three dense sentences, front-loaded with the action, then cost/timing, then the hand-off to show_thumbnails. Only the final clause about the Thumbnail tab and YouTube selection is slightly convoluted, though it still carries useful information.

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 two-parameter, credit-consuming generation tool with no output schema, the description covers cost, duration, prerequisite, downstream tool, and where results appear — everything an agent needs to invoke it correctly.

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?

Schema coverage is 100%, so both parameters are already documented, but the description adds real meaning: 'slots' refers to the a/b/c ideas produced by suggest_thumbnails rather than arbitrary values, and only user-requested slots should be passed. That linkage is not in the schema.

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 ('Draws the pictures for the chosen thumbnail ideas') and ties the slots directly to the output of suggest_thumbnails, so an agent can place it precisely in the thumbnail pipeline and distinguish it from suggest_thumbnails and show_thumbnails.

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 precondition ('slots a, b, c from suggest_thumbnails'), an explicit constraint ('only for the slots the user asked for'), an ordering requirement ('after saying the price'), and names the follow-up tool ('show_thumbnails shows them when done'). Both when-to-use and what-to-do-next are covered.

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

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