Skip to main content
Glama

list_posts_awaiting_my_review

Read-only

List the posts teammates have asked you to review that still need your verdict, most recently changed first. Covers every workspace on the account, not just the active one. Each post comes with its id, copy, channels and every reviewer's status. Returns up to limit posts (default 20, max 100). Act on one with approve_post or send_back_post, or leave a note with comment_on_post. This is not your own drafts (that is list_drafts), and not posts you sent to others for review.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_posts_awaiting_my_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax posts to return (1-100, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so safety is covered; the description still adds ordering ('most recently changed first'), the cross-workspace scope, the returned field set (id, copy, channels, reviewer statuses) and the cap (default 20, max 100). That is real added behavior beyond the structured fields, though it doesn't discuss pagination/truncation semantics when the cap is hit.

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?

Four tight sentences, scope and ordering front-loaded, then return shape, then routing to sibling tools. Every clause carries information the agent needs.

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, but the description compensates by enumerating the returned fields and the result cap, and it directs the follow-up actions. For a single-parameter read list with annotations, nothing material 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?

Only one parameter, and schema coverage is 100% — the schema already documents limit as 1-100, default 20. The description restates the same default/max without adding any new usage meaning (e.g., how to page past 100 or ordering interaction), so baseline 3 is appropriate.

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?

Specific verb + resource + qualifier: 'List the posts teammates have asked you to review that still need your verdict', with cross-workspace scope stated. It explicitly distinguishes itself from list_drafts and from posts you sent to others for review, so an agent can separate it from the many list_* siblings.

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?

Names the downstream actions explicitly ('Act on one with approve_post or send_back_post, or leave a note with comment_on_post') and the exclusions ('not your own drafts... not posts you sent to others'). The when-to-use and when-not-to-use are both spelled out with the alternative tools.

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