Skip to main content
Glama
Cassette-Editor

oh-my-cassette

cassette_run_job

Execute a single Cassette editing pass and block until settled. Returns the terminal envelope—succeeded, needs_user, review_required, exported, or failed—while streaming progress, eliminating extra polling.

Instructions

Run one Cassette edit turn and return when it is settled. This call IS the wait: it streams progress notifications while the agent works and answers with the terminal envelope (succeeded / needs_user / review_required / exported / failed). Do not poll cassette_job_status after it — that tool is for resuming a job whose call was interrupted. Pass wait=false only to deliberately detach the turn into the background.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
waitNo
modelNo
exportNo
promptNo
chat_idNo
messageNo
languageNo
selectorsNo
session_idNo
instructionNo
timeout_secNo
chat_messageNo
cassette_modelNo
thinking_levelNo
cassette_messageNo
cassette_languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
errorNo
phaseYes
job_idNo
warningsNo
artifactsNo
session_idNo
next_actionYes
Behavior4/5

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

With no annotations, the description carries full burden. It discloses streaming progress notifications, terminal envelope values (succeeded, needs_user, etc.), and the non-polling nature. It does not cover authorization or rate limits, but the behavioral core is well-stated.

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?

Three sentences, no fluff, front-loaded with the main action. Every sentence adds value, and the warning about polling is placed efficiently.

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

Completeness2/5

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

With 17 undocumented parameters, the description is too thin. The output schema exists but cannot compensate for missing parameter guidance. The agent would struggle to correctly fill parameters beyond 'wait'.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only explains the 'wait' parameter behavior. The other 16 parameters (url, model, prompt, etc.) receive no explanation, leaving the agent without guidance on how to use them despite the rich 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?

The description clearly states it runs one Cassette edit turn and waits for settlement, using 'Run one Cassette edit turn' as a specific verb+resource. It distinguishes from sibling cassette_job_status by explaining that tool is for resuming interrupted jobs.

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?

Provides explicit when-to-use (run a turn and wait) and when-not-to-use (do not poll cassette_job_status after this call). It also explains the alternative (use cassette_job_status for resuming interrupted jobs) and the wait parameter semantics for detaching.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cassette-Editor/oh-my-cassette'

If you have feedback or need assistance with the MCP directory API, please join our Discord server