XCut AI – Viral Content Research

Add a note to a canvas

xcut_add_note

Use this when the user wants a script, hook list, plan or other text saved to XcutAI. Accepts Markdown; with no canvas named it goes to the user's "From AI apps" canvas. Free. Do not use for calendar posts (use xcut_add_to_calendar).

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": {
      "text": "<text>"
    },
    "name": "xcut_add_note"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Markdown text.
`title`	No	Optional note title, e.g. "Week 1 scripts".
`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.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. The description adds real context beyond them: Markdown is accepted, an unnamed canvas silently falls back to the user's 'From AI apps' canvas, and the call is free. It does not disclose what the response contains (e.g. created note id or target canvas), which is the remaining gap.

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 with no filler, front-loading the trigger before the exception. Every clause carries decision-relevant information (accepted payload, default destination, cost, exclusion).

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?

For a simple single-payload write with no output schema and full annotation coverage, the description supplies trigger, default behavior, cost, and routing to the alternative sibling. The only omission is any hint about what is returned (note id, canvas location) or whether repeat calls create duplicates, given idempotentHint=false.

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 are already documented, including the Markdown format and the 'From AI apps' default for canvas_id. The description's mention of Markdown and the canvas fallback therefore largely restates structured data rather than adding syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 ('Add a note to a canvas') and enumerates the content types it accepts (script, hook list, plan, other text), so the agent knows the intended payload. It also explicitly names the sibling it is not (xcut_add_to_calendar), removing ambiguity within a 36-tool family.

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 a positive trigger ('when the user wants a script, hook list, plan or other text saved to XcutAI') plus an explicit exclusion with the correct alternative ('Do not use for calendar posts (use xcut_add_to_calendar)'). Nothing about tool selection is left to inference.

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?