Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Unschedule post

unschedule_post
Idempotent

Removes a scheduled post from the publishing schedule and returns it to draft status while preserving its text and media. Use it to cancel scheduled publishing without deleting content.

Instructions

Takes a post off the schedule. It becomes a draft and keeps its text and 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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "unschedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post's id, from list_posts or get_recording.
account_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-destructive, idempotent behavior, so the bar is lower. The description adds real value by disclosing the state transition (scheduled → draft) and that text and media survive, but says nothing about permissions, failure modes, or the role of the idempotency key.

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 short sentences, zero waste, with the primary effect front-loaded and the consequence second. Nothing could be cut without losing information.

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

Completeness3/5

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

For a 3-param mutation tool with no output schema, the description covers the essential before/after state well. It falls short on the undocumented idempotency_key and on error behavior when the post is not currently scheduled, which an agent calling this may hit.

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 coverage is only 33%, and the description adds no parameter meaning at all. post_id and account_id are well documented in the schema, but required idempotency_key carries no description anywhere, so an agent gets no guidance on generating or reusing it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Takes a post off the schedule') plus the resulting state ('becomes a draft and keeps its text and media'). That outcome implicitly distinguishes it from delete_post without naming it, though no sibling is explicitly referenced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: because the post survives as a draft, an agent can infer this is the reversible counterpart to delete_post. There is no explicit 'use this when X, not when Y' statement and no mention of what happens if the post was never scheduled.

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