Hook Detector

preview_package

Your package in a mock YouTube feed among a run's winners: view home, search, sidebar, phone (marks where a phone cuts the title) or tv; theme dark or light; look normal, grey or blur. Returns png_base64 and mine_at. Free. Same as POST /v1/packaging/preview.

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": {
      "title": "<title>"
    },
    "name": "preview_package"
  }
}

Input Schema

Name	Required	Description	Default
`look`	No
`seed`	No
`view`	No
`theme`	No
`title`	Yes
`topic`	No
`run_id`	No
`api_key`	No
`thumbnail`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses return fields ('png_base64 and mine_at'), cost ('Free'), and REST endpoint equivalence, but omits whether the operation is read-only, how api_key authentication works, rate limits, and whether previews persist.

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?

Three compact sentences front-loaded with the preview context, with no filler. The semicolon-packed option list is dense but efficient, and the parenthetical explaining the phone view adds useful detail without bloat.

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

Completeness2/5

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

For a 9-parameter tool with no annotations and 0% schema coverage, the description leaves major inputs (run_id, api_key, thumbnail, title semantics, topic, seed) and usage conditions unexplained. The output schema covers return format, but the description is not complete enough for reliable invocation.

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 0%, so the description must compensate for all 9 parameters. It usefully enumerates values for view (home/search/sidebar/phone/tv), theme (dark/light), and look (normal/grey/blur), but leaves seed, title, topic, run_id, api_key, and thumbnail unexplained.

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 conveys the resource: a package rendered as a preview in a mock YouTube feed across view/theme/look variants. It is clear enough to distinguish a rendering/preview operation, but it never uses an explicit action verb like 'generate' or 'render' and does not contrast with nearby siblings such as score_package or search_thumbnails.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance and names no alternatives. It lists preview options and says 'Free,' but an agent gets no help deciding between this and score_package, find_packaging, or search_thumbnails.

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?