Skip to main content
Glama
Sign In
PlanPost MCP Server

PlanPost MCP Server

by lukBB
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_post

Destructive

Edit a draft or scheduled social post’s content, media, schedule, platform overrides, and UTM settings without publishing it immediately.

Instructions

Update a draft or scheduled post. X (Twitter): nothing sent to X may contain a link (URL, bare domain or t.co) — not the post, any thread segment, or a first comment (posted to X as a reply). The X API bills each link post at $0.20 vs $0.015, so the API rejects them; put a link-free version in platformContent.twitter.

Input Schema

NameRequiredDescriptionDefault
idYesPost ID to update
utmNoPer-post UTM overrides. Pass `null` to clear all overrides (use user defaults). Omit to leave alone.
labelNoInternal working name shown in the dashboard. Pass null to clear. Never published.
mediaNoReplace the shared media array. Omit to leave existing media alone.
contentNoNew post text content
campaignNoRe-tag this post's campaign (sets utm.campaign). Pass null to clear.
postTypeNoExplicit post type; takes precedence over platformSettings flags. Same platform rules as create_post ('thread' is X/Twitter-only and needs threadSegments). Omit to leave the current type unchanged — a plain edit never downgrades a reel/short/story.
scheduleNoNatural-language reschedule: 'draft' (unschedule), 'today 20:30 Europe/Warsaw', 'tomorrow 07:00', 'in 2 hours', 'next week same time' (anchors on the post's current scheduled time). Use publish_post to publish immediately — 'now' is rejected here.
timezoneNoTimezone
scheduledForNoNew schedule time (ISO 8601), or empty string to unschedule
connectionIdsNoNew connection IDs
platformMediaNoPer-platform media overrides. Pass `null` to clear all overrides (every platform uses the shared `media` array). Omit to leave overrides unchanged.
threadSegmentsNoOrdered tweet segments for a thread (postType='thread'). 2–25 segments, each 1–280 characters.
platformContentNoPer-platform content overrides
platformSettingsNoPer-platform settings (e.g. { instagram: { isReel: true } }). TikTok posts need { tiktok: { privacyLevel } } (PUBLIC_TO_EVERYONE | MUTUAL_FOLLOW_FRIENDS | FOLLOWER_OF_CREATOR | SELF_ONLY) before they can be scheduled — this is how to repair a TikTok post that was created without one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds substantive behavior not in annotations or schema: the X API rejects any post/thread/comment containing a link, with the billing reason ($0.20 vs $0.015) and the workaround (link-free version in platformContent.twitter). Annotations already flag destructive/openWorld, so the bar is lower, but the description omits that media arrays are replaced wholesale and that partial failures are possible.

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?

Purpose is front-loaded in one short sentence, followed by the X-constraint block. The billing rationale is slightly verbose but earns its place by explaining why the constraint exists rather than just asserting it.

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 15-parameter destructive mutation with no output schema, the description covers only the X-link gotcha and the publish routing. It says nothing about how replacement semantics affect existing media/overrides, what the response returns, or how validation failures surface — those rely entirely on schema descriptions.

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 100%, so baseline is 3; the description adds real meaning on top by naming platformContent.twitter as the link-free escape hatch and by clarifying that schedule rejects 'now'. It says nothing extra about media replacement, utm, or connectionIds beyond the schema text.

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 ('Update a draft or scheduled post'), which also scopes what kinds of posts are editable. It does not explicitly distinguish from siblings like preview_post or create_post, though the publish_post hand-off gives implicit separation.

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 names the alternative for the immediate-publish case ('Use publish_post to publish immediately — now is rejected here'), which prevents a common misfire. Lacks guidance on when to use this versus create_post or preview_post, so usage is clear but not fully bounded.

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