Hook Detector

get_skeleton

The skeleton of a long find's whole video, heard by Scribe v2: sections, re-hooks, open loops, payoffs, sponsor and call-to-action spans, the outro, the timed lines. Builds it once for 5 credits as a paid call (status pending; read it with get_call); after that answers the stored one free. Same as POST and GET /v1/finds/{find_id}/skeleton.

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

Input Schema

Name	Required	Description
`api_key`	No
`find_id`	No	one of your long finds
`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.1/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that this is a paid mutation-like build (5 credits), that the result is asynchronous (status pending, read with get_call), and that subsequent reads are free from storage. It omits failure/refund behavior and any auth requirements, which keeps it below 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?

Front-loaded with the returned content, then cost and async semantics, with no filler. The trailing HTTP route reference is the one sentence that could be trimmed, and the first sentence is a long comma list.

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?

An output schema exists, so return values needn't be described; the description instead covers the things the schema cannot — credit cost, pending/async resolution via get_call, and free subsequent reads. Auth requirements and error paths remain unstated, a minor gap for a 3-param tool.

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 coverage is 67%, with find_id and idempotency_key already described in-schema. The description adds the caching model ('builds it once ... after that answers the stored one free') that motivates the idempotency key, but never mentions api_key and only implicitly scopes find_id to 'long finds'.

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 (the skeleton of a long find's whole video) and enumerates exactly what it contains: sections, re-hooks, open loops, payoffs, sponsor/CTA spans, outro, timed lines. An agent can distinguish it from get_find, remix_find, or find_long_hooks 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?

Explains the cost/behavior split clearly: the first call builds the skeleton for 5 credits and returns pending status, after which the stored version is free. It does not name an alternative sibling or state when-not to use it (e.g., when get_find already suffices), so it falls short of explicit routing guidance.

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?