XCut AI – Viral Content Research

Posting plan

xcut_posting_plan

Read-onlyIdempotent

Use this when the user wants a posting plan drafted from a niche, posting frequency and content pillars. It is a text plan only; to put posts on the user's XcutAI calendar use xcut_add_to_calendar. Free; no sign-in. Output is generic: for work based on the user's own posts, canvases or brand, use the signed-in XcutAI tools. Do not use for writing unrelated to social media or marketing content.

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": {
      "niche": "<niche>",
      "platform": "<platform>",
      "posting_frequency": "<posting_frequency>",
      "content_pillars": "<content_pillars>"
    },
    "name": "xcut_posting_plan"
  }
}

Input Schema

Name	Required	Description
`niche`	Yes	The creator's niche.
`platform`	Yes	Which platform the plan is for.
`content_pillars`	Yes	1 to 5 themes the account posts about.
`posting_frequency`	Yes	e.g. '3x/week', '1x/day'

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotent, and non-destructive, so safety is covered; the description adds genuinely new context: 'text plan only', 'Free; no sign-in', and 'Output is generic'. It stops short of describing the output shape or any length/rate constraints, which keeps it from a 5.

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 trigger ('Use this when...'), and each subsequent clause carries distinct routing or scope information rather than filler. Slightly dense with four separate directives, but none are redundant.

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 read-only, four-parameter text-generation tool with no output schema, the description covers trigger, scope, cost/auth posture, and alternatives well. It could say more about the output format, but the annotations and complete schema carry most of the remaining burden.

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 the schema already documents every parameter. The description names three of the four inputs (omitting platform) but adds no format or syntax detail beyond what the schema provides, so the baseline of 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 artifact ('posting plan drafted') plus the inputs that drive it (niche, posting frequency, content pillars). It explicitly distinguishes itself from xcut_add_to_calendar and the signed-in XcutAI tools, so an agent can route without reading 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?

Gives explicit when-to-use, when-not-to-use ('Do not use for writing unrelated to social media or marketing content'), and named alternatives for adjacent needs (xcut_add_to_calendar for scheduling, signed-in tools for personalized brand work). Nothing 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?