XCut AI – Viral Content Research

Generate an image

xcut_generate_image

Use this when the user wants a social media image made or edited: post graphic, carousel slide, thumbnail or ad visual, from a prompt and optional reference image links. Needs the Starter plan or higher; about 14 credits per image. Do not use for images unrelated to the user's content or marketing.

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": {
      "prompt": "<prompt>"
    },
    "name": "xcut_generate_image"
  }
}

Input Schema

Name	Required	Description	Default
`prompt`	Yes	What to make or change, e.g. "bold carousel cover: '3 retinol myths', pink gradient, large serif headline".
`aspect_ratio`	No	1:1, 4:5, 9:16, 16:9, 3:4 or 4:3. Default 1:1 (use 4:5 for Instagram feed, 9:16 for Reels and Stories).	1:1
`reference_image_urls`	No	Up to 5 public https image links to guide style or to edit.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true, non-idempotent, non-destructive, non-read-only, so the mutation/safety profile is covered. The description adds genuinely new context the annotations cannot: a Starter-plan gating requirement and a cost of about 14 credits per image. It stops short of describing the return value or any async/job behavior, 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 sentences, front-loaded with the usage trigger, then caveats. Every clause earns its place — use cases justify the tool's scope, the plan/credit line sets expectations, and the final sentence bounds misuse.

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 still gives an agent the trigger conditions, inputs, cost and plan gate — enough to call it correctly. It does not say what the call returns (image URL, asset, or job handle), which is the one thing an agent must recover elsewhere, likely via xcut_get_job.

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%, so prompt, aspect_ratio (with per-value guidance) and reference_image_urls are fully documented in the schema. The description only references 'a prompt and optional reference image links' and adds no syntax or constraint detail beyond it. Baseline 3 is correct 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 (made or edited) and resource (social media image), then enumerates concrete outputs — post graphic, carousel slide, thumbnail, ad visual — and names the inputs (prompt plus optional reference image links). An agent can distinguish this from every text-oriented sibling (write_caption, write_content) without opening the schema.

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?

Explicitly opens with 'Use this when the user wants a social media image made or edited' and closes with a when-not ('Do not use for images unrelated to the user's content or marketing'). No alternative tool is named, but no sibling performs image generation, so there is little routing ambiguity left.

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?