ClipFlux

Suggest a line in the script box

suggest_line

Read-only

Shows your suggested new words for one line of a draft's script inside the ClipFlux script box, beside the current line, with Use this line / Keep mine / Try another for the user. Changes nothing: the user's tap saves it. Call it when the user asks for a better line (the box's Suggest sends "Suggest a better line N"). Scene 0 is the hook. Write it under the script rules: one or two short sentences, at most 200 characters.

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>",
      "scene": "<scene>",
      "line": "<line>"
    },
    "name": "suggest_line"
  }
}

Input Schema

Name	Required	Description
`line`	Yes	Your suggested words for that line.
`scene`	Yes	The scene number from the script box; 0 for the hook.
`videoId`	Yes	The video id, from draft_video, list_my_videos or get_video.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'Changes nothing: the user's tap saves it' and, more valuably, discloses the interaction model — the suggestion is rendered with Use this line / Keep mine / Try another and is not persisted until the user acts. That is behavioral context an agent cannot get from the annotations.

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?

Front-loaded with what the tool does and what it does not change, then the trigger, then the content rules — a sensible order with no filler. It is a single dense paragraph, though, and the UI-button enumeration could be trimmed slightly.

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?

With no output schema, the description carries the burden of explaining the result, and it does so at the UI level (suggestion appears beside the current line, nothing saved). It does not say what the call returns to the agent itself, which is the one remaining gap for a 3-parameter write-adjacent tool.

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 the baseline is 3; the description adds meaning beyond it by constraining the content of `line` — 'one or two short sentences, at most 200 characters' — and by flagging that scene 0 is the hook. The per-parameter mapping is still implicit rather than explicit.

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?

Names a specific verb (suggests) and resource (one line of a draft's script) and states exactly where the result appears: in the ClipFlux script box beside the current line. This is clearly distinguishable from siblings like edit_draft or redo_scene, which modify rather than propose.

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?

Gives an explicit trigger — 'Call it when the user asks for a better line' — and even quotes the UI string ('Suggest a better line N') that precedes the call, plus the scene-0-is-the-hook convention. It stops short of naming an alternative sibling (e.g. redo_scene) or stating when not to use it, so it lands just below a 5.

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?