XCut AI – Viral Content Research

Import a social post

xcut_import_post

Use this when the user shares an Instagram, TikTok, YouTube or Facebook post or video link and wants its transcript, a breakdown of why it worked, or their own version of it. XcutAI transcribes the video and reads the caption, visuals and stats. Don't ask which canvas: with none named it goes to the user's "From AI apps" canvas. A fraction of a credit plus transcription (1-2 credits for a short video). Returns a job_id; xcut_get_job returns the transcript when done. Do not use for website links (use xcut_import_website) or Meta Ad Library links (use xcut_import_meta_ad).

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": {
      "url": "<url>"
    },
    "name": "xcut_import_post"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Post or video link.
`canvas_id`	No	Optional. Leave it out unless the user names a canvas: XcutAI then uses their "From AI apps" canvas. Ids come from xcut_list_canvases.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the mutation/idempotency profile; the description adds the operations behind the call (transcription, caption/visual/stat reading), the credit cost and its variability, the default canvas destination, and the async contract via the returned job_id resolved by xcut_get_job. This goes well beyond what the structured fields disclose.

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 use case, then cost, return contract, and exclusions in a tight sequence with no filler. The opening sentence is long, but every clause 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?

Despite having no output schema, the description explains the return value (job_id) and the follow-up tool needed to get the transcript. Combined with cost and canvas defaulting, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, but the description adds decision-relevant nuance: leaving canvas_id out silently routes to the user's "From AI apps" canvas rather than erroring. That is more than a restatement of the schema default.

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 (import) and a narrowly scoped resource (Instagram/TikTok/YouTube/Facebook post or video link), plus the outcomes it enables (transcript, breakdown, own version). An agent can distinguish it from xcut_import_website and xcut_import_meta_ad without opening any 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 condition (user shares a social post/video link wanting transcript or breakdown) and explicit exclusions with named alternatives for website links and Meta Ad Library links. It also preempts the canvas question, telling the agent not to ask when no canvas is named.

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?