Skip to main content
Glama

update_post

DestructiveIdempotent

Change a scheduled or draft post. DESTRUCTIVE WRITE: show the user a side-by-side of CURRENT vs PROPOSED and pass confirm=true only after explicit confirmation. Edit (default): caption, media, schedule, post_type, settings, account_id, or thread_posts; cannot edit published or currently publishing posts. account_id moves it to another account in the same workspace and brand (the platform follows). thread_posts replaces an X or Threads reply chain (2+ non-empty parts; the first is the caption). If a client already approved the post, a caption edit reopens caption approval, a media or thumbnail edit reopens asset approval, and a reschedule, account change, thread edit, or settings change reopens both. status (scheduled, paused, or draft, with scheduled_at when scheduling a draft): pause, resume, or move back to draft; send it on its own. A reconnect pause, including on X, resumes with status scheduled once the account is healthy, the time is in the future, and publishing is not paused. A billing pause, including on X, resumes once billing is clear, the time is in the future, and publishing is not paused. release_id (with optional group_id): set or repair external release/group IDs; send it on its own. approval_action (request, approve, request_changes, or reject): change client approval. Owner or admin only; the actor is the API key user, never a brand guest. request emails the brand reviewers; the others are team-side decisions. request_changes needs approval_note. Optional approval_axis is asset or caption; omit it for both. Send approval_action on its own. Pass the Version from get_post as expected_version and send only changed fields; a stale edit is refused.

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

Input Schema

NameRequiredDescriptionDefault
statusNoChange the post status instead of editing it. Send with post_id (and scheduled_at when scheduling a draft) only.
captionNo
confirmYesMust be true after the user explicitly confirms the proposed change.
post_idYes
group_idNoWith release_id only: an external group/campaign ID.
metadataNo
settingsNoPost settings. Instagram and X Article fields work here or in platform_settings: first_comment, user_tags, collaborators, is_trial_reel, caption_addon (poll or comment prompt; Facebook Login only, not Stories), article ({ title, cover }). Call list_platforms with view=schema and account_id for fields.
media_urlNoMedia URL. Posterly storage URLs are used as-is; third-party URLs are copied into posterly storage first.
post_typeNoOptional post type. Omit for auto-detection from media.
account_idNoMove this unpublished post to another account you can use in the same workspace. The account must belong to the post brand. The platform follows the new account.
media_urlsNoMedia URLs, handled like media_url.
release_idNoSet an external release ID instead of editing the post. Send with post_id and optional group_id only.
scheduled_atNoISO 8601 UTC. With status, required when scheduling a draft.
thread_postsNoReplace an X or Threads reply chain. At least 2 non-empty parts. The first part becomes the caption.
approval_axisNoWith approval_action approve, request_changes, or reject: which axis to decide. Omit for both. Not allowed with request.
approval_noteNoNote stored with the approval change. Required for request_changes.
reel_cover_urlNo
approval_actionNoChange client approval instead of editing the post. Send on its own.
expected_versionNo
platform_settingsNoPlatform-specific composer controls, flattened across platforms (unrelated fields ignored). Required: YouTube title; Pinterest board_id (cover_image_url also required for video Pins); Lemmy community. Accepted via passthrough but not listed below: Lemmy community/title, Dev.to canonical_url, Hashnode publication_id, Telegram parse_mode/disable_web_page_preview, Google Business post_type (STANDARD/EVENT/OFFER, alias topic_type), TikTok auto_add_music/photo_cover_index/media_type, Facebook post_type (incl. cover_photo), Mastodon language. Call list_platforms with view=schema and account_id for fields and examples.
reel_cover_methodNo
reel_thumb_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform_settings / properties / ai_generated / description
      Previous value: -"AI-content disclosure (TikTok is_aigc, X made_with_ai, YouTube containsSyntheticMedia, Pinterest ai_disclosures). Also serves as Bluesky hidden discovery tags via tags."New value: +"AI-content disclosure (TikTok is_aigc, X made_with_ai, YouTube containsSyntheticMedia, Pinterest ai_disclosures, Threads is_made_with_ai). Also serves as Bluesky hidden discovery tags via tags."
  2. Changed1 schema field changed
    • addedInput schema / properties / expected_version
      Added value: +{
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / platform_settings / properties / post_mode / description
      Previous value: -"TikTok delivery: auto (needs privacy_level) or inbox. Omitting both fields means inbox, with tiktok_inbox_implicit."New value: +"TikTok delivery: auto (default, unless the account is set to Finish in TikTok app) or inbox. With no privacy_level, auto uses the saved default or public."
  4. Changed2 schema fields changed
    • addedInput schema / properties / platform_settings / properties / post_mode
      Added value: +{
      +  "description": "TikTok delivery: auto (needs privacy_level) or inbox. Omitting both fields means inbox, with tiktok_inbox_implicit.",
      +  "enum": [
      +    "auto",
      +    "inbox"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / platform_settings / properties / privacy_level / description
      Previous value: -"TikTok privacy level."New value: +"TikTok audience for auto: PUBLIC_TO_EVERYONE, MUTUAL_FOLLOW_FRIENDS, FOLLOWER_OF_CREATOR, or SELF_ONLY."
  5. Changed2 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Move this unpublished post to another account you can use in the same workspace. The account must belong to the post brand. The platform follows the new account.",
      +  "type": "string"
      +}
    • addedInput schema / properties / thread_posts
      Added value: +{
      +  "description": "Replace an X or Threads reply chain. At least 2 non-empty parts. The first part becomes the caption.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "minItems": 2,
      +  "type": "array"
      +}
  6. Changed5 schema fields changed
    • changedInput schema / properties / approval_action / description
      Previous value: -"Change client approval instead of editing the post. Owner or admin only. The actor is the API key user, never a brand guest. Send on its own."New value: +"Change client approval instead of editing the post. Send on its own."
    • changedInput schema / properties / media_url / description
      Previous value: -"Media URL. Posterly storage URLs are used as-is; third-party HTTP(S) URLs are copied into posterly storage before the post is saved."New value: +"Media URL. Posterly storage URLs are used as-is; third-party URLs are copied into posterly storage first."
    • changedInput schema / properties / media_urls / description
      Previous value: -"Media URLs. Posterly storage URLs are used as-is; third-party HTTP(S) URLs are copied into posterly storage before the post is saved."New value: +"Media URLs, handled like media_url."
    • changedInput schema / properties / platform_settings / description
      Previous value: -"Platform-specific composer controls, flattened across all platforms (unrelated fields ignored). Required: YouTube title; Pinterest board_id (cover_image_url also required for video Pins); Lemmy community. Accepted via passthrough but not listed below: Lemmy community/title, Dev.to canonical_url, Hashnode publication_id, Telegram parse_mode/disable_web_page_preview, Google Business post_type (STANDARD/EVENT/OFFER, alias topic_type), TikTok auto_add_music/photo_cover_index/media_type, Facebook post_type (incl. cover_photo), Mastodon language. Call list_platforms with view=schema and account_id for the full field list and examples."New value: +"Platform-specific composer controls, flattened across platforms (unrelated fields ignored). Required: YouTube title; Pinterest board_id (cover_image_url also required for video Pins); Lemmy community. Accepted via passthrough but not listed below: Lemmy community/title, Dev.to canonical_url, Hashnode publication_id, Telegram parse_mode/disable_web_page_preview, Google Business post_type (STANDARD/EVENT/OFFER, alias topic_type), TikTok auto_add_music/photo_cover_index/media_type, Facebook post_type (incl. cover_photo), Mastodon language. Call list_platforms with view=schema and account_id for fields and examples."
    • changedInput schema / properties / settings / description
      Previous value: -"Post settings (same fields as platform_settings). For Instagram put first_comment, user_tags, collaborators, is_trial_reel, or caption_addon (poll or comment prompt, Facebook Login only, not Stories) here or in platform_settings. For an X Article put article ({ title, cover }) here or in platform_settings. Call list_platforms with view=schema and account_id for the field list."New value: +"Post settings. Instagram and X Article fields work here or in platform_settings: first_comment, user_tags, collaborators, is_trial_reel, caption_addon (poll or comment prompt; Facebook Login only, not Stories), article ({ title, cover }). Call list_platforms with view=schema and account_id for fields."
  7. Changed2 schema fields changed
    • addedInput schema / properties / platform_settings / properties / article
      Added value: +{
      +  "description": "X Article (needs an X Premium account): publish the caption as an Article. Pass null to turn Article mode off. The caption is the Markdown body (headings, bold, italic, lists, quotes, code blocks, tables, dividers); reference attached images with ![caption](media:1). Cannot be combined with poll, thread_posts, paid_partnership, video, or GIF.",
      +  "properties": {
      +    "cover": {
      +      "description": "Use the first attached image as the Article cover (default) or none.",
      +      "enum": [
      +        "first_image",
      +        "none"
      +      ],
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "Article title (required).",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "title"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / settings / description
      Previous value: -"Post settings (same fields as platform_settings). For Instagram put first_comment, user_tags, collaborators, is_trial_reel, or caption_addon (poll or comment prompt, Facebook Login only, not Stories) here or in platform_settings; call list_platforms with view=schema and account_id for the field list."New value: +"Post settings (same fields as platform_settings). For Instagram put first_comment, user_tags, collaborators, is_trial_reel, or caption_addon (poll or comment prompt, Facebook Login only, not Stories) here or in platform_settings. For an X Article put article ({ title, cover }) here or in platform_settings. Call list_platforms with view=schema and account_id for the field list."
  8. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is pre-supplied. The description still adds real value beyond that: the confirm gate, the side-by-side CURRENT vs PROPOSED requirement, the approval re-open matrix per field type, and stale-edit refusal on expected_version. However, the explicit confirm/side-by-side instructions largely restate what the destructiveHint annotation and the confirm parameter already convey, so this is additive context rather than fully independent disclosure.

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?

The destructive-write warning is correctly front-loaded and mode-by-mode organization makes a very dense block scannable. It is longer than ideal and packs multiple rules per sentence, but given 22 parameters and four distinct invocation modes, nearly every clause carries a rule an agent would otherwise have to infer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 22-parameter destructive mutation with no output schema and rich nested platform_settings, the description covers permissions, mode exclusivity, approval-reopen side effects, pause-resume conditions, and optimistic concurrency. An agent has enough to decide whether to call, how to confirm, and what will happen downstream.

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?

With 22 parameters and 68% schema coverage, the description does substantial compensatory work: it explains thread_posts replacement semantics and first-part-becomes-caption behavior, account_id cross-account moves and platform following, scheduled_at's requirement when scheduling a draft, approval_axis's omission meaning 'both', and expected_version's stale-edit refusal. Some parameters (metadata, portions of settings, reel cover fields) remain schema-only, which keeps it just below full marks.

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?

The description opens with a specific verb and resource ('Change a scheduled or draft post') and immediately names the operating modes (edit, status, release_id, approval_action). It also states the exclusion that matters most for selection — published or currently publishing posts cannot be edited — so an agent can distinguish this from create_post and delete_post without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each mode carries an explicit routing rule ('send it on its own') and the description names prerequisites for the tricky cases: reconnect and billing pauses resume only when the account is healthy and the time is in the future; approval_action is owner/admin only and the actor is the API key user. It also states the alternative path (pass expected_version and send only changed fields), which is exactly the when/how guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources