XCut AI – Viral Content Research

Find proven hooks

xcut_find_hooks

Read-onlyIdempotent

Use this when the user wants hooks, opening lines or first sentences for a post, Reel, TikTok, Short, YouTube video or ad. Returns proven hook templates matched to the topic, from XcutAI's library of about 1,000 hooks taken from posts that performed, each with slots for the user's subject. The library and topic search are in English. Free; no sign-in. Do not use for formats, script structures or platform facts (use xcut_get_playbook) or for a finished caption (use xcut_write_caption).

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": {
      "topic": "<topic>"
    },
    "name": "xcut_find_hooks"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many templates (default 8).
`topic`	Yes	What the post is about, in English. e.g. 'pricing mistakes for small bakeries'
`category`	No	Optional hook family to restrict to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new context: it is free, requires no sign-in, the library and topic search are English-only, and the library size (~1,000 proven hooks). That English-only constraint is material and not derivable from structured fields.

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?

Front-loads the trigger condition, then the return behavior, then the exclusions in a single dense paragraph with no filler. Slightly long but every sentence carries routing or behavioral information.

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?

There is no output schema, so the description must explain what comes back, and it does: proven hook templates matched to topic, each with slots for the user's subject. Combined with the when-to-use, language constraint and exclusions, an agent has everything needed to call 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 description coverage is 100%, with topic, limit and category all documented in-schema, so the schema carries the parameter burden and baseline 3 applies. The description only loosely echoes 'matched to the topic' and mentions slots, adding no format or syntax detail beyond what the schema already provides.

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+resource (find/return hook templates) with scope ('opening lines or first sentences') and even lists the supported output formats. It draws a clear boundary against xcut_get_playbook and xcut_write_caption, so an agent can tell it apart from the closest 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?

Explicit when-to-use ('when the user wants hooks...') plus explicit when-NOT with named alternatives ('Do not use for formats... use xcut_get_playbook', 'for a finished caption use xcut_write_caption'). Strong, but it does not differentiate from the near-identically named sibling xcut_hook_ideas, which is the most confusable tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XCut AI – Viral Content Research 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?