XCut AI – Viral Content Research

Get a content playbook

xcut_get_playbook

Read-onlyIdempotent

Use this when the user asks how to structure a Reel, TikTok, Short, YouTube video, carousel, caption, content plan, offer or ad, or how a platform's algorithm, hashtags or profile setup work. Call it before writing so the answer follows formats that performed. Returns a short summary of each matching video format, storytelling or retention principle, hook family, paid-ad framework or platform fact. Free; no sign-in. Describe the goal in plain English with platform and format. Do not use for hook templates (use xcut_find_hooks).

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": {
      "goal": "<goal>"
    },
    "name": "xcut_get_playbook"
  }
}

Input Schema

Name	Required	Description
`goal`	Yes	What is being made or decided, in English, with platform and format. e.g. 'instagram carousel that gets saved', 'tutorial reel structure', 'how many hashtags on instagram'
`kind`	No	Optional: structure (formats), principle, hook_type, ad_framework or platform_fact.
`limit`	No	How many entries (default 3).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeat-safety are covered structurally. The description adds genuinely new behavioral context: cost/access ('Free; no sign-in') and the shape of the response ('a short summary of each matching ... format, principle, hook family, ad framework or platform fact'). It omits rate limits or result-count caveats, but adds real value beyond the annotations.

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-loaded with the usage trigger, then return shape, then the exclusion; every sentence carries information. It is slightly dense with enumerations, but there is no filler or repetition.

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?

For a read-only, no-output-schema tool, the description supplies the trigger, the return content, the access cost, and the routing exclusion. Nothing an agent needs to select and invoke it correctly is missing.

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%, so all three parameters (goal, kind, limit) are already documented, including examples and bounds. The description's 'Describe the goal in plain English with platform and format' essentially restates the goal field's schema description rather than adding syntax or constraints, 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+resource ('get' a 'content playbook') and enumerates exactly what families it covers (Reel/TikTok/Short structure, principles, hashtags, ad frameworks, platform facts). It also names what it is not (hook templates), so an agent can separate it from xcut_find_hooks without opening either 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 an explicit trigger ('when the user asks how to structure ... or how a platform's algorithm, hashtags or profile setup work'), a timing rule ('Call it before writing'), and a negative case with the correct alternative ('Do not use for hook templates (use xcut_find_hooks)'). This is textbook 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?