Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Create post

create_post
Idempotent

Create a social media post draft with optional direct media links, then schedule it for a chosen time or next open slot after confirmation; without scheduling it remains an unpublished draft.

Instructions

Creates a social post as a draft, optionally with media from direct file links, and optionally scheduled for a time or the next open slot. Without a time it stays an unscheduled draft and nothing is published. With a time, the first call schedules nothing and returns needs_confirmation, will_happen (where and exactly when it will post) and confirmation; scheduling happens only on a second call with that confirmation. A non-empty not_done means the draft was saved but that step did not happen.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
captionNo
networkNo
timezoneNo
account_idNo
media_urlsNo
confirmationNo
scheduled_forNo
next_open_slotNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), the description discloses the critical non-obvious behavior: the first call schedules nothing and returns needs_confirmation/will_happen/confirmation, and scheduling only occurs on a second call. It also explains the partial-failure signal (non-empty not_done means the draft saved but the step did not happen), which annotations cannot convey.

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?

It is front-loaded with the core action and the draft/publish distinction, then layers the confirmation flow and failure semantics. Sentences are dense and long but nearly every clause carries information an agent needs; there is little 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 a ten-parameter mutation tool with no output schema, the description covers the highest-risk aspects: the two-step confirmation gate, what gets created (a draft), and the partial-failure return field not_done. It even names key return fields the agent must read. The gap is that most content parameters are left entirely to the schema.

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?

Measured schema description coverage is 0%, so the description must carry parameter meaning, and it only partially does. It explains scheduled_for and next_open_slot conceptually, the confirmation parameter, and that media comes from direct file links, but it says nothing about caption, network, timezone, account, or account_id. The inline anyOf descriptions in the schema rescue much of this, but the description itself adds meaning to only a subset of the ten parameters.

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?

The description opens with a specific verb and resource ("Creates a social post as a draft") and immediately scopes the two modes: draft-only versus scheduled. It distinguishes this from publishing behavior by stating "nothing is published," which implicitly separates it from publish_post_now and schedule_post, though it does not name those siblings explicitly.

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?

It clearly states when the tool produces an unscheduled draft versus a scheduled post, and spells out the exact two-call confirmation protocol including the condition (user has read will_happen and said yes). It does not explicitly route the agent to alternatives for editing or publishing an existing post, so the guidance is strong but not exhaustive.

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