Skip to main content
Glama

XCut AI – Viral Content Research

Add a post to the calendar

xcut_add_to_calendar

Use this when the user wants a planned post saved to their XcutAI content calendar: title, platform, type, date, and optionally caption and hashtags. Saved as a draft unless a status is given. Free. Do not use to post to social media: XcutAI does not post; when the user has posted it themselves, set status to published.

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": {
      "title": "<title>",
      "platform": "<platform>",
      "scheduled_at": "<scheduled_at>"
    },
    "name": "xcut_add_to_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort working title, e.g. "3 myths about retinol".
statusNodraft, in_review, approved, scheduled or published. Default draft. Setting it only records the status; it never posts.draft
captionNoFull caption or script text, if written.
hashtagsNoHashtags without spaces, e.g. ["#skincare", "#retinol"]. Up to 30.
platformYesWhere it will be posted: instagram, facebook, tiktok, youtube or meta (Meta ads).
canvas_idNoCanvas (UUID) the post belongs to. Optional.
post_typeNoFormat: post, image, video, carousel, reel, story, idea, script or ad. Default post.post
scheduled_atYesISO date or date-time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / description
      Previous value: -"draft, in_review, approved, scheduled or published. Default draft. Setting it never publishes anything."New value: +"draft, in_review, approved, scheduled or published. Default draft. Setting it only records the status; it never posts."
  2. Changed2 schema fields changed
    • addedInput schema / properties / scheduled_at / maxLength
      Added value: +64
    • addedInput schema / properties / scheduled_at / minLength
      Added value: +4
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds real context beyond them: the draft-by-default behavior, that it is free, and that it never posts. It does not warn about duplicate creation despite idempotentHint=false, which is the one remaining behavioral 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 tight sentences, front-loaded with the trigger condition, then the default behavior, then the exclusion. No filler.

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 an 8-parameter mutation tool with no output schema, the description covers purpose, defaults, cost, and the critical non-posting constraint. It does not say what is returned (e.g., a post id) or how to reference the created entry later, a minor gap given no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: status defaults to draft and only records state, and status should be set to published when the user has already posted. It omits canvas_id and post_type, which the schema covers adequately.

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 ('planned post saved to their XcutAI content calendar') and enumerates the core fields, so an agent can distinguish it from xcut_update_calendar_post or xcut_import_post at a glance.

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 when-to-use condition ('when the user wants a planned post saved'), an explicit when-not-to-use ('Do not use to post to social media'), and the alternative path (set status to published once the user has posted themselves).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources