Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Update post

update_post
Idempotent

Updates an existing post's text, network, or media, preserves scheduled time, and supports replacing or removing media; published posts cannot be changed.

Instructions

Changes a post's text, network or media. A scheduled post keeps its time. media_urls replaces all current media; remove_media=true removes it. A published post cannot be changed. A non-empty not_done says what did not happen, for example that the post is now an unscheduled draft.

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

Input Schema

NameRequiredDescriptionDefault
accountNo
captionNo
networkNo
post_idYesThe post's id, from list_posts or get_recording.
account_idNo
media_urlsNo
remove_mediaNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4/5.0
Behavior4/5

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

The description goes well beyond the annotations by disclosing a real data-loss behavior ('media_urls replaces all current media') and the partial-success contract ('A non-empty not_done says what did not happen'). The published-post restriction and preserved scheduling time add context the readOnly/destructive/idempotent hints do not convey. It doesn't mention required permissions or rate limits, keeping it at a 4.

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?

Five short sentences, each carrying a distinct operational fact, with the scope statement first and the destructive media behavior isolated for emphasis. Nothing is repeated from the schema or annotations.

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?

With no output schema, the description usefully explains that not_done reports partial failure, which the agent otherwise could not know. Combined with the published-post block and media replacement rule, it covers the mutation risk profile adequately, though idempotency_key and account selection semantics 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?

Schema description coverage is only 13% across 8 parameters, so the description has to carry weight. It adds real meaning for media_urls (replaces all media, not appends) and remove_media (deletes it), but says nothing about idempotency_key, caption limits, or network/account scoping behavior beyond the word 'network'. Partial compensation for a large coverage gap.

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 ('Changes a post's text, network or media') and names the exact fields that can be modified, so the agent knows this is a partial-mutation tool on an existing post. It doesn't explicitly contrast itself with siblings like copy_post_to_network or unschedule_post, so it stops short of a 5.

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?

'A published post cannot be changed' is an explicit exclusion that prevents a whole class of failed calls. 'A scheduled post keeps its time' clarifies the scheduling side-effect. It gives no positive guidance about which sibling to use when this tool doesn't apply (e.g., publish_post_now or copy_post_to_network), so it is not a full when/when-not map.

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