Skip to main content
Glama
Upload-Post

Upload-Post

Official

Edit a post awaiting approval

edit_pending_post

Modify a social media post while it awaits approval by updating its title, caption, platform-specific content, schedule, or cover image; only submitted fields change.

Instructions

Change a post while it waits for approval (its author or a reviewer). Same fields as editing a scheduled post: title and caption apply to every platform, platform_content {platform: {title, caption}} to some, fields holds other upload options by their form names, scheduled_date + timezone, cover_image_base64 / remove_cover (Instagram/Facebook Reels cover). Only what is sent changes. Every edit raises version by one. 409 approval_closed or approval_state_changed. Not generally available yet: until post approvals are switched on for the account, these calls answer 503 post_approvals_disabled (the feature is off, not a temporary failure).

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": {
      "approval_id": "<approval_id>"
    },
    "name": "edit_pending_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
fieldsNoOther upload options by their form field names.
captionNo
timezoneNoIANA timezone for scheduled_date.
approval_idYes`approval_id` from list_pending_approvals (also returned by an upload that went to approval).
remove_coverNo
scheduled_dateNoNew ISO 8601 date.
platform_contentNoPer-platform text, e.g. {"instagram": {"caption": "..."}}.
cover_image_base64NoNew Reels cover image, base64 or data URL.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations, it discloses partial-update semantics ("Only what is sent changes"), the version-bump side effect on every edit, the two specific 409 failure modes, and the feature-gate 503 with an explicit note that it is not a transient failure. That is exactly the kind of operational context an agent needs before attempting a mutation.

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?

Front-loaded with the core action and state, then errors and caveats in descending priority. Dense but nearly every clause carries information; the parenthetical asides (author-or-reviewer, Reels cover) add slight clutter but no wasted sentences.

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 9-parameter nested mutation with an output schema already covering return values, the description supplies the missing pieces: field precedence, partial-update behavior, versioning side effect, and the two blocking error states including the non-retryable feature gate.

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 67% schema coverage, the description compensates well by explaining the relationship the schema does not: title/caption are platform-agnostic while platform_content overrides per platform, and cover_image_base64/remove_cover are an Instagram/Facebook Reels-specific pair. It does not clarify timezone/scheduled_date interaction beyond naming them, but adds real meaning over the schema.

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?

"Change a post while it waits for approval" gives a specific verb plus the exact lifecycle state that scopes the resource, and it cross-references editing a scheduled post, which implicitly separates it from edit_post/edit_scheduled. An agent can pick this tool without opening the schema.

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 states the precondition clearly (the post is awaiting approval, caller is its author or a reviewer) and warns that the feature may be entirely unavailable via the 503 post_approvals_disabled path. It stops short of an explicit "use edit_post instead when the post is already published" exclusion, but the state-based framing makes the boundary inferable.

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