Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Schedule post

schedule_post
Idempotent

Schedule a draft post or reschedule it to a new time or the next free slot. Publishing happens automatically, and a confirmation step prevents mistakes.

Instructions

Schedules a draft, or moves a scheduled post to a new time, at scheduled_for or the account's next free slot (next_open_slot=true). The post publishes automatically at that time. The first call schedules nothing and returns needs_confirmation, will_happen (account, weekday, date, time and timezone) and confirmation; scheduling happens only on a second call with that confirmation.

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": "schedule_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post's id, from list_posts or get_recording.
timezoneNo
account_idNo
confirmationNo
scheduled_forNo
next_open_slotNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true); the description adds the non-obvious two-phase confirmation contract and the fact that the post publishes automatically at the chosen time. That is real behavioral context an agent could not infer from annotations or schema.

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?

Three sentences, front-loaded with the action and scope, then the publish behavior, then the confirmation flow. The parenthetical field enumeration ('account, weekday, date, time and timezone') is dense but each item is informative.

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 no output schema, the description covers the critical unknowns: the deferred-write flow and the shape of the first response. Gaps remain around idempotency_key usage and failure/conflict behavior, but nothing essential for a correct call is 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 description coverage is reported at 14%, so the description carries most of the burden — and it does explain the semantics of scheduled_for, next_open_slot, and confirmation, including the return fields of the first call. It says nothing about idempotency_key or account_id, leaving those to the schema.

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 plus both modes ('schedules a draft, or moves a scheduled post to a new time'), which cleanly separates it from unschedule_post, publish_post_now, and create_post. An agent can tell what it does without opening 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?

Explicitly routes between the two targeting modes ('at scheduled_for or the account's next free slot (next_open_slot=true)') and explains the two-call confirmation sequence. It stops short of naming sibling alternatives such as unschedule_post or publish_post_now, so the when-not guidance is implicit.

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