XCut AI – Viral Content Research

Import a website

xcut_import_website

Use this when the user shares a web page (product page, landing page, article) to use as context for writing their content. XcutAI reads the page and stores its text on a canvas. Up to about 3 credits. Returns a short preview. Do not use for social media post links (use xcut_import_post).

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_website"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Page 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.4/5.0

Behavior4/5

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

Annotations already declare the write/open-world/non-idempotent profile, so the bar is lower. The description adds real behavioral context beyond them: it stores text on a canvas, costs 'up to about 3 credits', and returns a short preview. It could say more about failure behavior (e.g. unreachable URLs), but the cost and storage disclosure is genuinely useful.

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 sentences with the use-case front-loaded, then behavior/cost, then the alternative. Every sentence carries distinct information 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 notes the return is a short preview, and it covers storage destination and cost. Combined with the safety annotations and full schema coverage, an agent has what it needs, though error handling is left unmentioned.

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 coverage is 100% and the canvas_id description already explains the default 'From AI apps' canvas and points to xcut_list_canvases. The description adds no additional parameter meaning beyond what the schema provides, 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?

The description names a specific verb and resource ('imports' a 'web page') and explicitly lists the page types covered (product page, landing page, article). It distinguishes itself from the sibling xcut_import_post, so an agent can route 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?

It states the triggering condition ('when the user shares a web page... to use as context for writing their content') and an explicit exclusion with the alternative named ('Do not use for social media post links (use xcut_import_post)'). This is exactly when-to-use, when-not, and the sibling to use instead.

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?