Skip to main content
Glama
Upload-Post

Upload-Post

Official

Approve a post

approve_post

Approve a team member's pending post to schedule or publish it to its platforms. Preview the exact output first, then confirm to send.

Instructions

Approve a team member's post waiting for approval: Upload-Post creates its scheduled job and publishes it to the post's platforms. Owner and Admin only. version is the item's version as reviewed; if the post was edited since, the call answers 409 approval_version_changed with the current item, which should be reviewed again. When it publishes: scheduled_date (+ timezone) if sent; now for immediate posts or with publish_now; the next free queue slot for queued posts; otherwise the post's own date. 409 approval_expired (an Editor's post whose date has passed), scheduled_date_in_past (a draft whose proposed date passed: send a date or publish_now), approval_closed; 429 when the monthly upload allowance is used up. 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). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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>",
      "version": "<version>"
    },
    "name": "approve_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoNote for the author.
versionYesThe item's `version` that was reviewed.
timezoneNoIANA timezone for scheduled_date.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
approval_idYes`approval_id` from list_pending_approvals (also returned by an upload that went to approval).
publish_nowNoPublish right away.
scheduled_dateNoISO 8601 date to publish at instead of the post's own.

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?

Goes well beyond the annotations by disclosing the full failure surface: 409 approval_version_changed with the current item, 409 approval_expired, scheduled_date_in_past, approval_closed, 429 allowance exhaustion, and 503 post_approvals_disabled as a permanent feature-off rather than a transient error. It also spells out the publish-time precedence rules, which the annotations do not cover.

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 purpose and the confirmation protocol, and nearly every sentence carries operative detail. The error-code enumeration and scheduling rules are packed into one dense paragraph, which is efficient but harder to scan than a structured list.

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 mutation tool with an output schema, it covers everything an agent needs: the two-step confirmation protocol, version-conflict handling, permission scope, feature-flag behavior, and rate limits. Return values are correctly left to the output schema.

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, but the description adds real meaning: `version` drives the 409 re-review loop, `confirmed` gates whether anything is sent, and `scheduled_date`/`timezone`/`publish_now` are ordered by an explicit precedence rule the schema does not state.

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?

States a specific verb and resource ('Approve a team member's post waiting for approval') and immediately describes the consequence (creates the scheduled job and publishes to the post's platforms). An agent can distinguish this from reject_post or withdraw_pending_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 Guidelines4/5

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

Gives explicit procedural guidance: call without `confirmed` first for a preview, show the user, then repeat with `confirmed: true`. It also states the Owner/Admin restriction and the preconditions for each outcome. It does not name sibling alternatives such as reject_post, which keeps it just short of a 5.

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