Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Unschedule Post

unschedule_post
DestructiveIdempotent

Remove a DRAFT or SCHEDULED post from the calendar without deleting it; the post becomes an undated DRAFT and will not publish. Reschedule later if needed.

Instructions

Take a DRAFT or SCHEDULED post off the calendar without deleting it: the post becomes an undated DRAFT (status DRAFT, scheduledAt null) and nothing publishes. Use it when the user wants to hold a scheduled post back; schedule it again later with publish_draft and a scheduledAt, and use delete_post only to drop it entirely. Any other status (PENDING, PUBLISHING, COMPLETED, FAILED, PARTIAL_FAILURE) fails with 400 because the post is already going out or out. A post whose YouTube video already waits on YouTube (scheduleOnYouTube) fails with 409 SCHEDULED_ON_YOUTUBE; delete it instead. Ids outside the workspace (the current one unless workspaceId names another) return 404. Safe to repeat on a post that is already an undated draft. Returns the post record.

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": {
      "id": "<id>"
    },
    "name": "unschedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID with status DRAFT or SCHEDULED, from list_posts or create_post
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesThe post record as an undated draft: id, status DRAFT, scheduledAt null, text, contentType, timezone, and platforms with per-target details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.6/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 corroborates and enriches these by spelling out the exact state transition, the 400/404/409 failure modes, the cross-workspace isolation rule, and the fact that repeats on an already-undated draft are safe. It does not restate annotation flags mechanically, though it stops short of describing latency or permission requirements.

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?

The core action and outcome are front-loaded in the first clause, then edge cases follow in descending priority. It is dense — long semicolon-chained sentences and a crowded error enumeration — but essentially no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with an output schema already covering return values, this covers the state transition, preconditions, failure codes, idempotency, and cross-tool alternatives. Nothing an agent needs to invoke it correctly appears to be missing.

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 already 100%, so the schema carries the parameter definitions; the description still adds real meaning by stating that ids outside the target workspace return 404 and by tying the id to a specific accepted status set (DRAFT or SCHEDULED). This is more than a restatement of the schema's field text.

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?

Opens with a specific verb+resource+scope: 'Take a DRAFT or SCHEDULED post off the calendar without deleting it', and immediately states the resulting state (status DRAFT, scheduledAt null). It is unambiguously distinguishable from delete_post and publish_draft, which it names.

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?

Explicit when-to-use ('when the user wants to hold a scheduled post back'), explicit alternatives with their own conditions (re-schedule via publish_draft, delete_post to drop entirely), and explicit when-not (any other status fails with 400, scheduleOnYouTube fails with 409).

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

Deploy Server

Other Tools