Skip to main content
Glama

List drafted replies awaiting review

list_pending_replies
Read-onlyIdempotent

Lists cloud patrol reply drafts for an account by status (pending by default; also sent, rejected, expired). Each pending draft has the target post, the drafted reply and an expiry 24 hours after it was drafted. Each call counts against the daily quota even when nothing is pending. Applies when review_before_reply is on and the user wants to decide what goes out.

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": {
      "account_id": "<account_id>"
    },
    "name": "list_pending_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNopending (default) | sent | rejected | expired
account_idYesAccount id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower; the description still adds non-obvious behavior: each call consumes daily quota even when the result is empty, and pending drafts expire 24 hours after drafting. It also previews what a pending record contains. It does not mention pagination or ordering.

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?

Front-loaded with purpose and filter, then quota and expiry caveats. Four sentences, all carrying information; minor redundancy between 'pending by default' in prose and the schema enum.

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 describing the shape of a pending draft (target post, drafted reply, expiry). Combined with the quota warning and the activation condition, an agent has everything needed to decide and call correctly.

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 description coverage is 100%, so both parameters are already documented, and the description mostly restates the status enum ('pending by default; also sent, rejected, expired') and account scoping. Baseline 3 is appropriate; no extra syntax or semantics are added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (lists) and resource (cloud patrol reply drafts) plus the filtering dimension (status) and the pending default. It is clearly distinguishable from approve_pending_reply/reject_pending_reply by being a read/list operation, though it never names those siblings explicitly.

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?

Gives a concrete activation condition: 'Applies when review_before_reply is on and the user wants to decide what goes out.' That tells the agent when this list is relevant, but it does not name the follow-up alternatives (approve/reject) or state when to skip it in favour of them.

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.