XCut AI – Viral Content Research

Import a Meta ad

xcut_import_meta_ad

Use this when the user shares a Meta Ad Library link (facebook.com/ads/library) and wants the ad's copy, media and video transcript to study or remix. Holds up to 18 credits and charges the real cost. May return a job_id for xcut_get_job. Do not use for organic Facebook posts (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_meta_ad"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Meta Ad Library link (facebook.com/ads/library/?id=…).
`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 only declare the generic safety profile (readOnlyHint=false, openWorldHint=true, non-destructive). The description adds non-obvious behavior: an 18-credit hold charging the real cost, and that it may return a job_id to be polled via xcut_get_job. It stops short of describing retry/idempotency behavior or failure modes, so a 4 rather than 5.

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: the trigger first, the cost/return behavior second, the exclusion last. No filler, and the important routing constraint is front-loaded.

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 compensates by disclosing the possible job_id return and the polling tool. Combined with 100% schema coverage for both params, an agent has what it needs; only deeper detail on the job flow or credit-failure behavior 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% and both parameters are documented in the schema, including the canvas_id fallback behavior and the xcut_list_canvases id source. The description only restates the Meta Ad Library link requirement, so it adds no meaning 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?

States a specific verb and resource ('Import a Meta ad') plus what is extracted (copy, media, video transcript) and names the sibling it is not (xcut_import_post). An agent can distinguish it from xcut_import_post and xcut_import_profile 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 Meta Ad Library link') and an explicit exclusion with the correct alternative ('Do not use for organic Facebook posts (use xcut_import_post)'). Both when-to-use and when-not-to-use are covered.

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?