Skip to main content
Glama

approve_post

Returns a link the user opens to approve a post they have been asked to review. A verdict belongs to the reviewer, and approving a required review can be the last thing standing between a draft and publication, so this tool does NOT approve: it returns a link the user opens to read the copy and press Approve themselves. Show them the link and wait. Do not try to confirm on their behalf. There is no argument that does that, and any you invent is ignored. Any note waits with the link and is saved only when the user presses Approve. The link works once and expires in 30 minutes; until then the review stays pending. Use list_posts_awaiting_my_review to find what's pending; to ask for changes instead, use send_back_post.

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

Input Schema

NameRequiredDescriptionDefault
noteNoOptional note to the author, saved with the approval once the user presses Approve.
post_idYesThe id of the post to approve
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / note / description
      Previous value: -"Optional note recorded with the approval"New value: +"Optional note to the author, saved with the approval once the user presses Approve."
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description carries real weight — and it delivers the non-obvious traits: the link is single-use, expires in 30 minutes, the review stays pending until then, and a supplied note is only persisted when the user presses Approve. It does not clarify why a read-like operation carries readOnlyHint=false, though the note-persistence and pending-state behaviour are broadly consistent with a non-read-only hint, so no contradiction.

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?

The key constraint — that this returns a link rather than approving — is front-loaded in the first sentence, and the routing hints close it out. A few lines are rhetorically repetitive ('There is no argument that does that, and any you invent is ignored'), but they defend against a high-cost failure mode rather than padding.

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?

There is no output schema, and the description covers exactly what comes back (a link), its lifetime and single use, the pending state during that window, and what the caller should do with it. For a three-parameter tool with full schema coverage this leaves nothing an agent needs 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 the baseline is 3, but the description adds genuine meaning: the `note` waits with the link and is only saved on approval, and it pre-empts inventing a 'confirm' argument by stating none exists and would be ignored. The `workspace` parameter is left entirely to its schema text.

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?

The description states a specific verb and resource — it returns a one-time approval link for a post the user has been asked to review — and explicitly says it does NOT perform the approval. That framing alone separates it from send_back_post and list_posts_awaiting_my_review 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?

It gives explicit when-to-use routing (list_posts_awaiting_my_review to find pending items, send_back_post to request changes instead) and an explicit when-not-to-do behaviour ('Show them the link and wait. Do not try to confirm on their behalf'). The agent is told what it must not attempt and why no parameter can substitute.

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