XCut AI – Viral Content Research

Hook ideas

xcut_hook_ideas

Read-onlyIdempotent

Use this when the user wants 10 new hook variations written for their niche and topic on YouTube, TikTok or Instagram. For proven hook templates from posts that performed, use xcut_find_hooks. Free; no sign-in. Output is generic: for work based on the user's own posts, canvases or brand, use the signed-in XcutAI tools. Do not use for writing unrelated to social media or marketing content.

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": {
      "platform": "<platform>",
      "niche": "<niche>",
      "topic": "<topic>"
    },
    "name": "xcut_hook_ideas"
  }
}

Input Schema

Name	Required	Description
`niche`	Yes	The creator's niche, e.g. "fitness for busy moms".
`topic`	Yes	What the post is about.
`platform`	Yes	Where the hooks will be used.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world traits. The description adds real value beyond them: it discloses the access model ('Free; no sign-in'), that output is generic rather than personalized, and that signed-in tools exist for brand-specific work. It stops short of describing rate limits or exact return formatting.

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 sentences, front-loaded with the primary trigger, followed by the alternative, the access model, and the exclusion. Every sentence earns its place, though it is slightly dense with multiple conditionals packed together.

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

Completeness4/5

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

No output schema exists, so the description carries the return-value burden and does reasonably well, stating the count (10), the nature (generic vs. personalized), and the free/no-sign-in access. It leaves the exact output format unstated, but the essentials for correct invocation are present.

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 self-documenting parameters and a platform enum. The description restates niche/topic/platform at a high level but adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 applies.

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 and resource ('10 new hook variations written for their niche and topic') plus the platforms involved. It explicitly differentiates itself from sibling xcut_find_hooks, letting an agent route without opening a schema.

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?

Gives both positive triggers (user wants new hook variations for a niche/topic) and negatives ('Do not use for writing unrelated to social media or marketing content'), and names the alternative tool for proven templates. This is explicit when/when-not/alternative guidance.

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?