Skip to main content
Glama
Sign In

Leadpoet

by com.leadpoet
OverviewDiscussionsAdmin

List queued messages

listQueuedMessages
Read-onlyIdempotent

Lists queued-message previews, including messages in paused campaigns. MCP defaults to 25 per page; follow next_cursor for more. A page is not the queue size: the first page's queued_total is the count the Queued screen shows (active campaigns), and queued_including_paused adds paused ones. getOutreachAnalytics live.in_flight counts only approved messages about to send in active campaigns, not paused ones or Preparing drafts. getSendForecast's queued count splits by channel, paused campaigns included. Previews omit full content and sending controls. REST calls without limit or cursor retain the legacy snapshot, capped at 200 with results_limited when incomplete.

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

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

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, and the description adds real value on pagination (25 default, follow next_cursor), the distinction between queued_total and queued_including_paused, and the legacy REST cap of 200 with results_limited. What it does not disclose is ordering of results or what fields a preview actually contains; with annotations covering the safety profile, a 3 is appropriate.

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 purpose is front-loaded in the first sentence and the count-reconciliation sentences earn their place by preventing an agent from confusing three overlapping queue counts. It is dense and slightly sprawling, but no sentence is pure padding.

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 nested-parameter list tool with no output schema, the description covers defaults, pagination, response field meanings (queued_total, queued_including_paused, next_cursor, results_limited), and legacy REST behavior. The remaining gap is filter semantics and preview field contents, which is acceptable given the rich inline schema descriptions.

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?

The schema nests everything under query, so top-level coverage reads as 0% and the description must compensate. It partially does: it explains limit/cursor paging semantics, the pagination default, and the legacy include_message_id path, but filter parameters such as icps, senders, channels, campaigns, and inbox_search get no added meaning beyond their 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?

States a specific verb and resource (list queued-message previews) plus scope (includes paused campaigns), and explicitly distinguishes its counts from getOutreachAnalytics live.in_flight and getSendForecast's per-channel queued count. An agent can pick this over those siblings without opening a 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 gives clear situational routing: use this for the queued-screen count and previews, use getOutreachAnalytics for approved-in-flight counts, use getSendForecast for per-channel splits. It also warns that previews omit full content and sending controls, implying a detail tool is needed for that, though it doesn't name it or give explicit exclusions.

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