XCut AI – Viral Content Research

Repurpose content

xcut_repurpose_content

Read-onlyIdempotent

Use this when the user wants one piece of content turned into TikTok, Reel, LinkedIn, X and email angles. 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": {
      "title": "<title>"
    },
    "name": "xcut_repurpose_content"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Title of the piece to repurpose.
`description`	No	What the piece covers, optional but gives better angles.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered elsewhere. The description adds genuinely new context the annotations cannot express: no sign-in/auth requirement, free cost, and a quality caveat that output is generic versus brand-aware signed-in tools. It stops short of describing return format, but that is a minor gap against an already-covered safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the trigger condition. Every sentence carries distinct information: trigger, cost/auth plus quality caveat, and exclusion. No filler.

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 two-parameter, read-only generation tool with no output schema, the description covers everything an agent needs: when to invoke, auth/cost posture, output quality expectations, routing to alternatives, and scope boundaries. Nothing material 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% with only two parameters, so the schema already fully documents 'title' and 'description'. The description mentions 'one piece of content' but adds no syntax, format, or length guidance beyond the schema. Baseline 3 is appropriate.

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?

Names a specific transformation ('one piece of content turned into TikTok, Reel, LinkedIn, X and email angles'), not just a verb+resource. It also distinguishes itself from the signed-in XcutAI tool family, so an agent can tell it apart from siblings like xcut_write_content without opening schemas.

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 wants one piece of content turned into...'), an explicit alternative ('for work based on the user's own posts, canvases or brand, use the signed-in XcutAI tools'), and an explicit exclusion ('Do not use for writing unrelated to social media or marketing content'). All three of when/when-not/alternative are present.

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?