Hook Detector

create_poll

Put 2 to 4 packages to Hook Detector's users, who pick the one they would click, blind. Closes at votes_wanted or after 7 days. 2 credits, given back when a picture cannot be stored. Results with get_poll. Same as POST /v1/polls.

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": {
      "options": "<options>"
    },
    "name": "create_poll"
  }
}

Input Schema

Name	Required	Description
`api_key`	No
`options`	Yes	2 to 4 packages, each {title, thumbnail}: a title of 1 to 100 characters and a JPEG, PNG or WebP in base64 or an i.ytimg.com URL
`subject`	No	what the video is about
`question`	No	default: Which would you click?
`votes_wanted`	No	10 to 200, default 30
`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

A3.8/5.0

Behavior4/5

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

With no annotations present, the description carries the burden and does well: it discloses that polls auto-close at votes_wanted or after 7 days, that the call costs 2 credits, and that credits are refunded when an image cannot be stored. Missing only auth/permission expectations, which the api_key parameter hints at but the description never explains.

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?

Four short sentences, all load-bearing: purpose, lifecycle, cost, and result retrieval. Front-loaded with the core action. The opening phrasing ('Put 2 to 4 packages to Hook Detector's users') is slightly awkward but not costly.

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?

An output schema exists, so return values need not be described. Given that, the description covers the essentials an agent needs: what is being created, limits on options, when the poll terminates, credit cost and refunds, and where results come from.

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 83%, so the schema already documents options, subject, question, votes_wanted and idempotency_key in detail. The description adds real meaning only for votes_wanted, explaining that it triggers closure of the poll, rather than adding syntax or format guidance beyond the schema.

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?

States a concrete verb and resource: it creates a blind preference poll over 2-4 thumbnail packages for the platform's users. The key constraints (2-4 options, blind pick) make it distinguishable from vote_poll and get_poll, though it never contrasts itself with the sibling ab_set, which sounds like a related comparison tool.

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?

Usage context is implied rather than stated: you use this when you want audience feedback on competing thumbnails, and 'Results with get_poll' correctly routes the agent to the retrieval counterpart. There is no explicit guidance on when NOT to use it, nor any mention of how it differs from ab_set or why to pick one over the other.

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?