Hook Detector

share_run

Share a finished Short form run as a public, read-only page anyone can open with the link, no sign-in: each hook's spoken line, on-screen words, idea, plays, creator and its video, in the Hook Detector skill page layout. Nothing about the account is on it.

Returns {"run_id", "token", "url"}; give the person the url
(https://hookdetector.com/p/<token>). Idempotent: a run keeps one link, so calling again
returns the same url. The same body as POST /v1/runs/{run_id}/share; the page's data is
GET /v1/shared/{token}, no key needed. Needs the write scope. Free.
Errors: 404 run_not_found, 409 run_not_finished while the run works (call get_run with
wait_seconds=50 first), 409 run_not_shareable for a failed run or a Long form or
Packaging run, 422 invalid_request for a malformed run_id.

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

Input Schema

Name	Required	Description	Default
`run_id`	No
`api_key`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.7/5.0

Behavior5/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 so: it discloses idempotency (one link per run, repeat calls return same url), the write scope requirement, that it is free, the exact error codes and meanings, and that no account data appears on the page. That is rich behavioral context beyond what any structured field provides.

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?

Front-loads the outcome, then returns, then idempotency, then API equivalence, then constraints and errors. Dense but every sentence informs a decision; no filler.

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

Completeness5/5

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

Even though an output schema exists, the description helpfully specifies the exact return shape and the URL template, plus the companion GET endpoint. Combined with the error taxonomy, an agent has everything needed to call and interpret this correctly.

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 0%, so the description must compensate. It gives useful meaning to run_id via the URL path and the 422 run_not_found/invalid_request errors, but the api_key parameter is never mentioned beyond an oblique 'needs the write scope'. Partial compensation only.

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 verb (Share) and resource (a finished Short form run) and precisely characterizes the output: a public, read-only page with no sign-in showing each hook's spoken line, on-screen words, idea, plays, creator and video. This is clearly distinguishable from sibling tools like export_run or showcase.

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?

Explicitly routes the agent: 409 run_not_finished says call get_run with wait_seconds=50 first, and 409 run_not_shareable excludes failed runs, Long form, and Packaging runs. The when/when-not conditions are concrete rather than implied.

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?