Hook Detector

clean_recording

The talking-head cleaner (15 credits), like 1of10's AutoCut: silences tightened, retakes, false starts, stutters and fillers cut with a reason on every cut, other microphones or cameras synced to the first, as Premiere XML, FCPXML and a CMX 3600 EDL. Takes 1 to 4 file_id values staged with POST /v1/clean/files (a chat cannot send the file itself). Runs as a job; get_call reads it. Same as POST /v1/clean.

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": "clean_recording"
  }
}

Input Schema

Name	Required	Description
`files`	No
`api_key`	No
`idempotency_key`	No	1 to 255 visible ASCII characters; the same key and request within 24 hours answer the saved remix and charge nothing; the same key with another request is 422 idempotency_key_reused

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 15-credit cost, the 1-to-4 file limit, async job execution with get_call polling, the staging requirement, and the output artifacts. It omits failure modes and what happens if staging is skipped, which keeps it short of a 5.

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 mostly front-loaded, with cost and capability in the opening clause and operational constraints trailing. The 'like 1of10's AutoCut' comparison is the one sentence fragment that doesn't earn its place, and the single sentence is a run-on, but overall little is wasted.

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?

For a three-parameter async job tool with an output schema and no annotations, the description covers cost, prerequisites, job polling and output formats, which is enough for an agent to invoke it correctly. Slight redundancy in re-listing output formats that the output schema likely defines, and no note on failure behavior.

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 only 33%, so the description must compensate; it explains that 'files' takes 1 to 4 file_id values that must first be staged via POST /v1/clean/files, which is the critical semantics the bare array schema lacks. Only api_key is left unexplained, and its name is self-evident; idempotency_key is already documented 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?

The description names a specific operation ('talking-head cleaner') and enumerates exactly what it produces: silenced tightened, retakes/false starts/stutters/fillers cut, multicam synced, delivered as Premiere XML, FCPXML and CMX 3600 EDL. An agent knows precisely what the tool does and what it returns without opening any 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?

It states key preconditions: files must be staged with POST /v1/clean/files because 'a chat cannot send the file itself,' and that it runs as a job read via get_call. It also maps itself to the REST equivalent ('Same as POST /v1/clean'). It stops short of naming when to prefer this over sibling review/edit tools, but the prerequisite routing is unusually explicit.

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

All Hook Detector 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?