XCut AI – Viral Content Research

Update a calendar post

xcut_update_calendar_post

DestructiveIdempotent

Use this when the user wants to change a post on their XcutAI calendar: date, caption, hashtags, title, type or status (for example mark it approved). Only the fields given change; their old values are not kept. Free. Do not use to publish: XcutAI never posts to social media.

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": {
      "post_id": "<post_id>"
    },
    "name": "xcut_update_calendar_post"
  }
}

Input Schema

Name	Required	Description
`title`	No	New title.
`status`	No	New status: draft, in_review, approved, scheduled or published. Never publishes anything.
`caption`	No	New caption or script text.
`post_id`	Yes	Id (UUID) of the calendar post, from xcut_list_calendar.
`hashtags`	No	New hashtag list; replaces the old one. Up to 30.
`post_type`	No	New format: post, image, video, carousel, reel, story, idea, script or ad.
`scheduled_at`	No	New date and time in ISO 8601, e.g. "2026-11-03T18:00:00Z".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / scheduled_at / anyOf

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

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 destructiveHint=true and idempotentHint=true; the description goes beyond them by explaining partial-update semantics ('Only the fields given change') and what is destroyed ('their old values are not kept'), plus a cost signal ('Free') and a no-publishing guarantee. It omits error behavior and any permission/auth requirements, so it is strong but not exhaustive.

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 short sentences, front-loaded with the use condition, then the mutation semantics, then the negative constraint. No filler; every sentence carries distinct information.

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 7-parameter mutation tool with full schema coverage and safety hints in annotations, the description covers when to use it, partial-update behavior, cost, and the publishing caveat. The only gap is that with no output schema the agent gets no hint about what a successful response contains or how to confirm the change.

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 per the rubric the baseline is 3. The description names the updatable fields and matches the schema properties, but adds no format or syntax detail beyond what each property description already provides.

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 (change/update), the resource (a post on the XcutAI calendar), and enumerates the mutable fields: date, caption, hashtags, title, type, status. This clearly separates it from xcut_add_to_calendar and xcut_delete_calendar_post without requiring 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?

Gives a concrete triggering condition ('when the user wants to change a post on their XcutAI calendar') and an explicit exclusion ('Do not use to publish: XcutAI never posts to social media'). It does not name a sibling alternative for the add/update boundary, so it stops short of a full 5.

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?