Skip to main content
Glama
Upload-Post

Upload-Post

Official

Reject a post

reject_post
Destructive

Reject a pending team post to prevent publication and notify the author with a rejection comment; only owners and admins can use it.

Instructions

Reject a team member's post waiting for approval: it will not be published and the author is notified with the comment. Owner and Admin only. A rejected post cannot be reopened. 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>",
      "comment": "<comment>"
    },
    "name": "reject_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentYesWhy it is rejected; shown to the author.
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?

Annotations already flag destructiveHint=true and non-idempotency, and the description adds substantial context on top: irreversibility, the author-notification side effect, permission gating, and two distinct failure modes including a feature-flag 503 that is explicitly not transient. The preview-before-send requirement is a behavioral constraint the agent could not infer from annotations.

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 effect and outcome, then permissions, then error conditions, then the confirmation protocol. It is dense but every sentence carries operational information; only minor tightening would be possible given the amount of required detail.

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, and the description still covers permissions, irreversibility, side effects, error codes, and the safety protocol. Nothing an agent needs to invoke this destructive tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters including the preview/confirm semantics of `confirmed` and the origin of `approval_id` are already documented in the schema. The description restates the confirmed flow usefully but adds no new syntax or constraints beyond the schema, so baseline 3 applies.

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 ('Reject a team member's post waiting for approval') plus the concrete outcome: it will not be published and the author is notified with the comment. This clearly separates it from approve_post and withdraw_pending_post without needing their schemas.

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?

Gives explicit preconditions (Owner and Admin only), explicit state limits ('a rejected post cannot be reopened'), and a mandatory conversational protocol: call without `confirmed` for a preview, show the user, then repeat with `confirmed: true`. It also names the error cases (409 approval_closed, 503 post_approvals_disabled) that tell the agent when not to proceed.

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