Skip to main content
Glama

request_review

Ask one or more teammates to review a draft before it publishes. Required reviewers block publishing until every one approves. Optional reviewers are FYI: they can comment or approve but won't block the post. Composition must already exist as a draft (use save_draft first). Optionally pre-schedule the post at the same time. A workspace may let only people in it review its posts; anyone else is refused by name.

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>",
      "reviewers": "<reviewers>"
    },
    "name": "request_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional message to the reviewers
post_idYesThe id of the post to send for review
reviewersYesList of teammates to review. Provide email, user_id, or name per reviewer.
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.
scheduled_atNoOptional ISO 8601 time. The post auto-publishes at this time IF all required reviewers have approved.

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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, open-world call; the description adds substantive behavior on top: required reviewers hard-block publishing, optional reviewers never block, the draft prerequisite, the conditional nature of scheduled_at, and that non-workspace reviewers are refused by name. It does not say whether reviewers are notified or what a partial/invalid reviewer list returns, which keeps it off a 5.

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?

The core action and its blocking semantics are front-loaded in the first two sentences, with prerequisites and edge cases (draft requirement, scheduling, workspace membership) following in order of importance. No sentence is filler, and every clause adds operative information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with annotations but no output schema, the description covers preconditions, blocking semantics, scheduling behavior, and the cross-workspace refusal case. The main omission is any hint of the success/failure response shape or whether reviewers are notified, which an agent might want before calling.

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 coverage is 100% and the per-field descriptions already explain name/email/user_id resolution and the required flag's default, so the schema carries most of the burden. The description's contribution is the consequence-level meaning of those flags ('block publishing until every one approves'), which is useful but largely mirrors what the schema states.

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 first sentence gives a specific verb and resource ('Ask one or more teammates to review a draft') and pins the timing ('before it publishes'), which distinguishes it from siblings like approve_post or send_back_post that act on an already-in-review post. An agent can identify the operation 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?

It states an explicit prerequisite ('Composition must already exist as a draft (use save_draft first)'), explains the required-vs-optional reviewer distinction in terms of blocking behavior, and flags the optional pre-schedule path. It stops short of naming the counterpart siblings (approve_post, list_posts_awaiting_my_review) for the review lifecycle, so routing guidance is clear but not complete.

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