Hook Detector

write_upload_pack

The upload pack (1 credit) for a long find or your video: a description with chapters that pass YouTube's rules, tags and hashtags. Runs as a job. Same as POST /v1/seo.

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

Input Schema

Name	Required	Description
`url`	No	a YouTube link: watch, youtu.be or shorts address
`links`	No
`api_key`	No
`find_id`	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

B3.4/5.0

Behavior3/5

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

With no annotations, the description adds important behavioral context by stating that the tool costs 1 credit and runs as a job, and that it is equivalent to POST /v1/seo. However, it does not disclose authentication expectations, job-result retrieval, or retry behavior, leaving meaningful gaps for a credit-consuming job tool.

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?

The description is compact and front-loads the core purpose and cost before adding job behavior and API equivalence. The phrase 'Same as POST /v1/seo' is a bit cryptic for an agent without API context, but overall it is efficient.

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?

The description covers what the tool produces, its cost, and its job-based execution, which is useful given no annotations. But for a five-parameter job tool with low schema description coverage, it omits how to choose parameters and how to retrieve the job result, leaving the definition only moderately complete.

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 40%, and the description does little to compensate. It loosely implies choosing between a 'long find' and 'your video,' but does not explain how that maps to find_id versus url, nor does it clarify links or api_key.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as an upload pack and specifies its contents: a description with chapters, tags, and hashtags for a long find or video. It distinguishes itself from sibling writing tools such as write_titles and write_script by output type, though it does not explicitly name alternatives.

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 gives a clear use context: 'for a long find or your video,' which tells the agent when this tool is appropriate. It does not provide explicit exclusions or name alternative tools, but the target use case is adequately conveyed.

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?