XCut AI – Viral Content Research

Write with an XcutAI agent

xcut_write_content

Use this when the user wants XcutAI's agents to write for their brand: Reels, TikTok and Shorts scripts, YouTube scripts, Facebook posts, Meta ad copy, hooks, captions or plans, using their brand memory, imported posts and XcutAI's library of formats that performed. The conversation is saved to their canvas. Pick agent for the platform, or auto. Token-billed (typically 1-26 credits). Longer turns return a job_id. Do not use for writing unrelated to the user's 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": {
      "request": "<request>"
    },
    "name": "xcut_write_content"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	No	Which XcutAI writer to use: auto (picks from the request), instagram, tiktok, youtube_script, youtube_shorts, facebook, meta_ad or general. Default auto.	auto
`request`	Yes	What to write, as the user would ask in the canvas chat.
`item_ids`	No	Only use these canvas items (default: the whole canvas).
`canvas_id`	No	Optional. Leave it out unless the user names a canvas: XcutAI then uses their "From AI apps" canvas, where imports also land. Ids come from xcut_list_canvases.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover only the safety profile (non-read-only, non-idempotent, non-destructive, closed-world). The description adds genuinely new behavioral context: token-billed at typically 1-26 credits, the conversation is persisted to the user's canvas, and longer turns return a job_id instead of the content directly. These are exactly the traits an agent needs before invoking a billed generative write.

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?

Front-loaded with the use condition, then deliverable scope, then picks, then billing/return behavior, then the exclusion. The deliverable list is long but each item earns its place by defining scope precisely, and there is no filler.

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?

With no output schema, the description correctly compensates by explaining that a canvas conversation is created and that long turns return a job_id (resolvable presumably via xcut_get_job). Billing cost is also disclosed. Minor gap: it does not say what the short-turn return value looks like, but it is otherwise complete for a 4-parameter mutation tool.

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 four parameters (including the agent enum and the canvas_id lookup source) are already documented in the schema. The description's "Pick `agent` for the platform, or auto" largely restates the enum, and item_ids is not addressed at all, so 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?

States a specific verb+resource (XcutAI agents writing brand social content) and enumerates the concrete deliverables (Reels/TikTok/Shorts scripts, YouTube scripts, Facebook posts, Meta ad copy, hooks, captions, plans). This clearly separates it from siblings like xcut_write_caption (single narrow output) and xcut_rewrite_bio or xcut_repurpose_content.

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?

"Use this when the user wants XcutAI's agents to write for their brand" plus an explicit exclusion ("Do not use for writing unrelated to the user's social media or marketing content") gives clear when/when-not guidance. It does not name an alternative sibling for the overlapping caption-writing case, so it falls short of a 5.

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?