Clipwright

List moves

list_moves

Read-only

Browse and filter available motion and graphics moves for script lines by beat, content, mood, surface, or skill, then inspect each move’s purpose and credit cost before planning visuals.

Instructions

The catalogue of moves (motion and graphics) for script lines: moves of make_ugc, make_faceless and plan_reference_remake. Filter by beat, content, surface, mood, skill or q; each line has the move's purpose and credits per use (0 is free). names=a,b answers those in full (data to pass, what the line needs). Read it before planning the visuals. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_moves"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No
`beat`	No
`mood`	No
`limit`	No
`names`	No
`skill`	No
`cursor`	No
`detail`	No
`content`	No
`surface`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.45.0Nov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare a safe read operation, and the description adds genuinely new behavior: each row carries the move's purpose and per-use credits where 0 is free, the call itself is free, and names=a,b switches to full detail. It omits pagination behavior, which is the main remaining gap.

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?

Dense and front-loaded, with cost and the read-before-planning cue early. The parenthetical 'names=a,b answers those in full (data to pass, what the line needs)' is cryptic and slightly muddies the sentence.

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

Completeness3/5

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

Given ten parameters, zero schema descriptions and no output schema, the definition covers the filter semantics and output contents well but says nothing about the cursor/limit pagination pair or when to choose detail=short versus full. An agent could still call it correctly, but would be guessing on paging and verbosity.

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 0%, so the description must carry parameter meaning; it explains q, beat, content, surface, mood, skill and the special names=a,b mode, but leaves limit, cursor and the short/full detail enum unexplained. Partial compensation for a 10-parameter tool with six enums.

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 resource and scope: 'the catalogue of moves (motion and graphics) for script lines', and ties it to the three consumer skills (make_ugc, make_faceless, plan_reference_remake). An agent can tell what it returns without opening 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?

Gives an explicit timing cue — 'Read it before planning the visuals' — and lists the filter dimensions to narrow by. It does not name an alternative tool or say when not to use it, which keeps it just under a 5.

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

Deploy Server