Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Delete post

delete_post
DestructiveIdempotent

Deletes a draft or scheduled post from the calendar after a confirmation step; published posts remain on the network.

Instructions

Deletes a post from drafts and the calendar. A post already published stays on the network. The first call deletes nothing and returns needs_confirmation, will_happen and confirmation; deletion 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": "delete_post"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.4/5.0
Behavior5/5

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

With destructiveHint, openWorldHint, and idempotentHint already declared, the description still adds behavior the annotations cannot encode: the deliberate no-op first call, the three return fields (needs_confirmation, will_happen, confirmation), and the fact that published posts survive the delete. That is exactly the kind of safety-critical context a destructive tool needs beyond its annotations.

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 short sentences, zero filler, with the scope constraint and the danger (published posts survive) front-loaded before the mechanics. Every sentence carries distinct information.

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 destructive, open-world tool with no output schema, the definition covers the confirmation protocol and the fields returned by the first call, which is what an agent must know to behave safely. It is slightly incomplete in not explaining idempotency_key's role or what errors/reversibility look like, but nothing essential to calling it correctly 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 coverage is only 25%, so the description must carry weight, and it does for the riskiest parameter by explaining the two-call confirmation contract and that the same arguments must be reused. It adds nothing for idempotency_key (undocumented in both places) or account_id, and it does not say where post_id comes from beyond the schema's own note, so it falls short of full compensation.

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?

"Deletes a post from drafts and the calendar" states a specific verb, resource, and scope, and the follow-up sentence delimits what is NOT deleted (a published post stays live on the network). An agent can distinguish this from publish_post_now or unschedule_post without opening any schema.

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?

The definition gives a clear procedural rule for the confirmation flow (first call returns will_happen and confirmation; act only after the user clearly says yes), which is strong guidance. However, it never routes the agent between this tool and near-siblings such as unschedule_post (remove from calendar without deleting) or delete_campaign_signal, so the choice of tool is left to inference.

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