Skip to main content
Glama

List messages sent to a lead

list_lead_messages
Read-only

The emails and texts already exchanged with one lead, newest first, including whether each was delivered, so a new message need not repeat or contradict something they already received.

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": {
      "lead_id": "<lead_id>"
    },
    "name": "list_lead_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, default 20, ceiling 100
lead_idYesThe lead to message, an id as returned by list_leads or get_lead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lead_id / description
      Previous value: -"The lead to message. Get one from list_leads or search_contacts."New value: +"The lead to message, an id as returned by list_leads or get_lead."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond them: results are ordered newest-first and each item carries delivery status, which tells the agent what it will see and how to reason about recency.

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?

A single sentence, front-loaded with the resource and ordering, ending with the reason to call it. The trailing clause is slightly wordy but every part carries information; nothing is wasted.

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?

With no output schema, the description does its share by disclosing ordering and the presence of per-message delivery status. Pagination limits are left entirely to the schema, and nothing about the shape of individual messages (subject, body, timestamps) is hinted at, which is a minor gap for a two-parameter list tool.

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% — lead_id is explained as an id from list_leads or get_lead, and limit documents the default 20 and ceiling 100. The description adds nothing about either parameter, so the baseline 3 applies.

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?

The description names the resource precisely — emails and texts already exchanged with one lead — which is enough for an agent to distinguish it from send_lead_email/send_lead_sms, which are about sending rather than reading. The verb is implicit ("the emails and texts already exchanged") rather than an explicit "list", which is why it isn't a 5.

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 a clear situation for use: check history before composing a new message so you don't repeat or contradict prior contact. No explicit exclusions or named alternative tools are given, so it stops short of the when/when-not bar.

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