Hook Detector

recreate_thumbnail

New thumbnails for your video with a YouTube video's own thumbnail as the layout reference (2 to 4 images, every printed word checked); priced as make_thumbnails. Same as POST /v1/thumbnails/recreate; read it with get_thumbnails.

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": {
      "video_url": "<video_url>"
    },
    "name": "recreate_thumbnail"
  }
}

Input Schema

Name	Required	Description
`mode`	No
`size`	No
`count`	No
`title`	No
`words`	No
`api_key`	No
`video_url`	Yes
`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 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses cost ('priced as make_thumbnails') and a quality behavior ('every printed word checked'), plus the 2–4 image output constraint. It omits whether generation is async/job-based, whether api_key is mandatory, and what happens to previously generated thumbnails.

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?

A single dense sentence plus an API mapping and read-path hint; the differentiating mechanism is front-loaded and nothing is padding. Slight terseness ('2 to 4 images') leaves the constraint's target ambiguous.

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?

An output schema exists, so return values needn't be spelled out, and the cost disclosure is valuable for a credit-consuming generation tool. However, for an 8-parameter, zero-annotation mutation tool, the description leaves too many parameters and the async/completion model unexplained.

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 only 13% across 8 parameters, so the description must compensate. It conveys count semantics ('2 to 4 images') and hints at words ('every printed word checked') and video_url (layout reference source), but mode, size, title, and api_key are left entirely undefined in both schema and description.

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 operation (generate new thumbnails) plus a distinctive mechanism: the source YouTube video's own thumbnail serves as the layout reference, with 2 to 4 images and every printed word checked. It also differentiates from siblings by naming make_thumbnails (same pricing) and get_thumbnails (read path), so an agent can choose without opening other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a workflow ('read it with get_thumbnails') and notes pricing parity with make_thumbnails, which helps compare cost. But it never states when to prefer this over make_thumbnails, edit_thumbnail, or search_thumbnails, nor any prerequisites beyond the idempotency note in the schema.

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?