Skip to main content
Glama

Update post

update_post

Edit the caption and/or media of a DRAFT (created in the Flomixy app or through the API) or of a post created through the API that is not yet published, and/or set or change the first comment (and its delay) and, on THREADS targets, the topicTag (null removes it) of individual existing targets via targets. Scheduled or published posts created in the app are refused (403), published posts cannot be edited (409) and a published first comment is locked. Needs the POSTS_WRITE scope and a member allowed to edit posts (posts:edit). On a WORDPRESS target the article fields (title, contentHtml/contentMarkdown, excerpt, slug, categories, tags, wpStatus, featuredImage, featuredImageAlt) can be edited the same way, only the ones you send change; once the article is published, any such edit is refused (409). Approval and the set of targets cannot be changed. Optional recyclingEnabled (+ recyclingIntervalDays/MaxRepeats/ExpiresAt) toggles Evergreen recycling and, unlike caption/media, works on an already-published post; requires the POSTS_RECYCLE scope.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe post id.
captionNoNew caption. The limit depends on the targeted networks.
targetsNoExisting targets whose first comment to set/update (per-target firstComment / firstCommentDelayMinutes), or whose WORDPRESS article fields (title, contentMarkdown, featuredImage, ...) to edit.
mediaUrlsNoNew media URLs (http/https only).
mediaTypesNoNew media types.
recyclingEnabledNoEvergreen: toggle re-drafting this post every recyclingIntervalDays once (or after) it is PUBLISHED. Unlike caption/media, this can be set on an already-published post. Requires an API key with the POSTS_RECYCLE scope (403 otherwise).
recyclingExpiresAtNoStop recycling after this instant (ISO 8601 with time zone); must be in the future. Omit for never.
recyclingMaxRepeatsNoStop recycling after this many re-drafts. Omit for unlimited.
recyclingIntervalDaysNoDays between recycles. Required when enabling and the post has no interval stored yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full load and does so well: required scopes (POSTS_WRITE, posts:edit, POSTS_RECYCLE), the 403/409 refusal conditions, the partial-update semantics ('only the ones you send change'), locked published first comments, and the immutable approval/target-set constraint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is valuable but delivered as one long run-on sentence with heavy parenthetical stacking and ALL-CAPS emphasis, making it hard to parse. Nothing is clearly wasted, but restructuring into eligibility / editable-surface / side-effect blocks would make it far more skimmable.

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 9-parameter mutation tool with no output schema and no annotations, it covers scope, error conditions, per-channel quirks, and partial-update behavior. The main gap is that it never says what the call returns or whether the response reflects the updated post.

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 the baseline is 3; the description nonetheless adds meaning beyond it — per-target grouping for first comment vs WORDPRESS fields, 'null removes it' for topicTag, that recyclingIntervalDays is needed when enabling with no stored interval, and that recycling is the one field valid on published posts.

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 ('Edit the caption and/or media of a DRAFT ... or of a post created through the API that is not yet published') and enumerates the distinct editable surfaces (caption/media, first comment plus delay, topicTag, WORDPRESS article fields, recycling). This clearly separates it from create_post/create_draft_post/reschedule_post, which do different things.

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 gives explicit eligibility rules (drafts, API-created unpublished posts; app-scheduled/published posts refused with 403; published posts 409) plus the notable exception that recycling works on already-published posts. It does not name sibling alternatives, so it falls short of a 5, but the when/when-not conditions are unusually thorough.

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