Skip to main content
Glama

approve_post

Destructive

Approve the current step of 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 (steps approve in order); a forbidden error means the user isn't an approver for this step yet — tell them who needs to approve instead, don't retry. If this is the last step, the post is finalized immediately (moves to scheduled or posting). If steps remain, the post stays in_approval and the next step's approvers are notified. Pass step_order: the current_step that get_post_approval shows (the step the user reviewed). Then a repeated call, for example after a timeout, never approves the next step too: it answers step_changed with the step the review is on now. On step_changed, call get_post_approval again and ask the user before you decide on the new step.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe post ID to approve (must have approval_status 'pending')
step_orderNoThe workflow step the user reviewed: current_step from get_post_approval. When the review is on another step now, nothing is approved 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 approved and the answer is step_changed.",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint/openWorldHint) by disclosing the authorization rule (must be a listed approver for the CURRENT step, steps approve in order), the state transitions (finalize to `scheduled`/`posting`, or stay `in_approval` and notify next approvers), and the idempotency guard via `step_order` returning `step_changed` instead of approving the next step.

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?

Purpose and precondition are front-loaded, and every sentence carries operational value (authorization, finalization, idempotency, error recovery). The step_order/idempotency explanation is however stated twice — once in the 'Pass step_order' sentence and again in the schema — so it is slightly longer than needed.

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 state-mutating, order-sensitive approval tool with no output schema, the description covers preconditions, authorization, side effects, success states, and named error outcomes (`forbidden`, `step_changed`) with next actions. An agent has everything required to call it correctly and to handle failures.

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 already 100%, so the baseline is 3; the description adds the intent behind `step_order` ('the step the user reviewed') and the reason to pass it (a repeated call must not advance the workflow). It largely restates the schema's own step_changed explanation, so it earns a 4 rather than a 5.

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 the current step of a post's approval workflow') and immediately scopes it to posts with approval_status 'pending' / status `in_approval`. An agent can distinguish this from reject_post or update_post purely from the description's workflow-step framing.

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?

Explicitly says to check `get_post` first, requires pending status, points to `get_post_approval` for the step to pass, and prescribes recovery behavior on `step_changed` ('call get_post_approval again and ask the user'). It also rules out retrying on `forbidden` and names the alternative action (tell the user who must approve).

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