Skip to main content
Glama

reject_post

Reject a post's approval workflow. Only works on a post with approval_status 'pending' (post status in_approval) — check get_post first. IMPORTANT: only succeeds if the connected user is a listed approver for the workflow's CURRENT step (same requirement as approve_post). Unlike approval, a rejection stops the WHOLE workflow immediately, not just the current step — the post's status becomes rejected and it will not publish. Pass comment to explain why; it's shown to the requester and other approvers in the post's review thread. Pass step_order (the current_step from get_post_approval) as with approve_post; on step_changed, read the review again before you decide.

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": "reject_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe post ID to reject (must have approval_status 'pending')
commentNoOptional reason for the rejection, shown to the requester and other approvers.
step_orderNoThe workflow step the user reviewed: current_step from get_post_approval. When the review is on another step now, nothing is rejected and the answer is step_changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / step_order
      Added value: +{
      +  "description": "The workflow step the user reviewed: current_step from get_post_approval. When the review is on another step now, nothing is rejected and the answer is step_changed.",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only give the generic safe-mutation profile (readOnlyHint=false, destructiveHint=false); the description carries the real behavioral weight: the whole workflow stops, the post becomes `rejected`, and it will not publish. It also discloses the approver-identity requirement and that the comment is surfaced to the requester and other approvers in the review thread.

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

Conciseness5/5

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

Front-loaded with the action and scope, then preconditions, authorization, side effects, and parameters in descending order of decision value. Every sentence contributes a constraint or an outcome; no filler or restatement of the name.

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?

No output schema exists, and the description compensates by naming the observable outcome (`rejected` status, no publish) and the `step_changed` response case. For a one-required-parameter mutation gated by approver identity, nothing an agent needs in order to call it correctly 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 description coverage is 100%, so baseline is 3, but the description adds cross-tool meaning: `step_order` is the `current_step` from get_post_approval used identically as in approve_post, and on mismatch nothing is rejected and the answer is `step_changed`. `comment` visibility to requester/approvers is reinforced as consequence, not just format.

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 post's approval workflow') and immediately contrasts it with the sibling approve_post ('Unlike approval, a rejection stops the WHOLE workflow immediately'). An agent can distinguish this from approve_post, update_post, and delete_post without opening any schema.

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 (only on approval_status 'pending' / status `in_approval`), a prerequisite step ('check `get_post` first'), an authorization gate (connected user must be a listed approver for the CURRENT step), and recovery guidance ('on `step_changed`, read the review again before you decide'). It also names the equivalent sibling approve_post for the shared step_order convention.

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