Skip to main content
Glama
Sign In

Leadpoet

by com.leadpoet
OverviewDiscussionsAdmin

List drafts awaiting review

listReview
Read-onlyIdempotent

Lists drafts waiting for human review, each with the revision needed to approve, deny or skip it, plus contacts and sends that need attention. Filter by channel, sender, campaign, ICP or product. MCP defaults to 5 drafts. Follow next_cursor for more.

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / properties / senders / description
      Previous value: -"Comma-separated sending account IDs (each account's id from listSendingAccounts), or unassigned. On listCampaigns this lists the campaigns that send from those accounts."New value: +"Comma-separated sending account IDs (each account's id from listSendingAccounts), or unassigned. Keeps what those accounts send, such as their campaigns."
  2. Changed1 schema field changed
    • changedInput schema / properties / query / properties / senders / description
      Previous value: -"Comma-separated IDs from the outreach filter catalog."New value: +"Comma-separated sending account IDs (each account's id from listSendingAccounts), or unassigned. On listCampaigns this lists the campaigns that send from those accounts."
  3. Changed1 schema field changed
    • addedInput schema / properties / query / properties / message_id
      Added value: +{
+  "description": "Only this draft. Pass inbox_paused=true to include one in a paused campaign.",
+  "format": "uuid",
+  "type": "string"
+}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the default page size of 5 under MCP and the requirement to follow next_cursor to see more, which is a behavioral detail the annotations do not carry.

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?

Three compact sentences with the core purpose front-loaded, then filters, then pagination. Nothing is redundant, though the phrase 'contacts and sends that need attention' is somewhat vague for the space it takes.

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 read-only list tool with no output schema, the description covers what comes back, how to filter, and how to paginate, which is most of what an agent needs. The remaining gap is the per-draft addressing parameters (message_id, inbox_paused) that would matter when re-fetching a single item.

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?

Top-level schema coverage is reported at 0% and the single 'query' wrapper is undocumented, so the description must compensate and largely does by naming the five filter facets and the limit/cursor behavior. It leaves message_id, inbox_paused and the filtered flag unexplained, so it is not fully complete.

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 and resource ('Lists drafts waiting for human review') and even describes what each returned item carries (the revision needed to approve, deny or skip it). It is clearly not a summary or a mutation tool, though it never names a sibling to contrast against (e.g. getReviewSummary).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives implied usage context by enumerating the filter dimensions ('Filter by channel, sender, campaign, ICP or product') and the pagination behavior. It offers no when-not guidance and no explicit pointer to alternatives such as getReviewSummary or listQueuedMessages, so the agent must infer the choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Leadpoet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources