Skip to main content
Glama
Upload-Post

Upload-Post

Official

Withdraw a post awaiting approval

withdraw_pending_post
Destructive

Withdraw or discard a post awaiting approval so it will not be published and its media is deleted; this action is irreversible.

Instructions

Withdraw (its author) or discard (a reviewer) a post waiting for approval: it becomes withdrawn, will not be published and its media is deleted. It cannot be undone. 409 approval_closed when it was already decided. 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>"
    },
    "name": "withdraw_pending_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).

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 past the destructiveHint annotation: it discloses that media is deleted, that the action is irreversible, the exact error codes for already-decided and feature-disabled cases, and that a 503 here means the feature is off rather than a transient failure. That last note prevents a realistic retry mistake.

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-loads the action and consequences, then the error conditions, then the confirmation protocol. Dense but every clause carries operational information; the account-gating sentence is long but warranted.

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?

An output schema exists, so return values need not be explained. Given a destructive, gated, two-phase mutation, the description covers consequences, irreversibility, error states and the required user-approval flow — nothing material is missing.

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, and the description earns above that by framing `confirmed` as part of a two-step preview-then-commit workflow and noting that nothing is sent without it. The approval_id sourcing is left to the schema's own description.

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?

Opens with a precise verb+resource and even splits semantics by actor: withdraw for the author, discard for a reviewer. It states the resulting state (withdrawn, not published, media deleted), so an agent knows exactly what the operation does 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?

Gives a concrete invocation protocol (call without `confirmed` first, show the preview, then repeat with `confirmed: true`) and explains the 409 approval_closed condition. It stops short of naming sibling alternatives such as reject_post or edit_pending_post, so the agent must infer that path itself.

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