XCut AI – Viral Content Research

List calendar posts

xcut_list_calendar

Read-onlyIdempotent

Use this when the user asks what content is planned or scheduled: posts on their XcutAI content calendar between two dates, optionally for one canvas, with status (draft, in review, approved, scheduled, published). Free. Do not use for posts already live on social media (use xcut_profile_analytics).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xcut_list_calendar"
  }
}

Input Schema

Name	Required	Description
`end`	No	ISO date, e.g. 2026-10-31.
`limit`	No	Most posts to return, 1-200. Default 60.
`start`	No	ISO date, e.g. 2026-10-01.
`canvas_id`	No	Only posts planned for this canvas (UUID). Omit for all canvases.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026

changedInput schema / properties / end / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 64,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / start / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 64,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

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 readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety and repeatability are covered structurally. The description adds genuine behavioral context beyond that: the call is free (no credit cost) and enumerates the status taxonomy the listing spans. It stops short of noting pagination/ordering behavior beyond the schema's limit, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, and the trigger condition and scope constraints are front-loaded ahead of the exclusion. Nothing is repeated from the schema.

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?

There is no output schema, so the description carries return-shape burden, and it partly discharges this by naming the status taxonomy the posts carry. All parameters are optional and documented, and the alternative route is given. What is still missing is any hint of default ordering or result-volume behavior, which matters slightly for a list tool with a 200-item cap.

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%, with formats, defaults and the 1-200 limit range documented inline, so the structured data does the heavy lifting and the baseline is 3. The description echoes date range and the optional single-canvas scoping but adds no syntax or semantics beyond the schema, and its mention of status values risks reading as a filter that does not exist among the four parameters.

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+resource (list posts on the XcutAI content calendar) and pins the scope precisely: between two dates, optionally one canvas, with defined status values. It also names the sibling it is not (xcut_profile_analytics for live posts), so an agent can separate it from other listing/analytics tools without opening a 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?

Opens with an explicit trigger ('Use this when the user asks what content is planned or scheduled') and adds an explicit exclusion with a redirect ('Do not use for posts already live on social media (use xcut_profile_analytics)'). This is the when/when-not/alternative pattern at full strength.

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?