Skip to main content
Glama
agentisend

agentisend

List contacts

list_contacts
Read-onlyIdempotent

Retrieve contacts already linked to the account, filter by email or audience, and page results ordered newest first.

Instructions

Purpose: look up the people this account already has a relationship with. Pass an email to find one. NOT for: finding addresses to contact for the first time. This product has no feature for that and will not grow one. Returns: each contact with its properties, newest first.

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_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoLook up one contact by address.
limitNoPage size (1-100).
cursorNonext_cursor from the previous page. Omit for the first page.
audience_idNoLimit the list to one audience. The id is a segment on this account. A value that is not an audience id lists every contact on the account.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value with "each contact with its properties, newest first," which discloses return ordering not present in the structured fields. It says nothing about pagination behavior or what an unmatched email yields.

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?

Three labeled lines (Purpose / NOT for / Returns) with zero filler and the key scoping statement up front. Every sentence carries information an agent needs.

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?

Given an output schema exists, the description need not detail return values, yet it still summarizes ordering and shape. Annotations cover safety. Minor gap: no mention of how paging interacts with the email lookup or what an empty result means.

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 all four parameters are already documented, including the notable audience_id fallback behavior. The description only echoes the email lookup, adding essentially nothing beyond the schema; 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?

States a specific verb and resource ("look up the people this account already has a relationship with") and narrows it further with "Pass an email to find one." It does not name a sibling tool as the alternative, but the explicit "NOT for" boundary does most of the differentiating work.

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 clear positive trigger (existing relationships) and an explicit exclusion (first-time contact discovery, which it says the product will not support). The exclusion points at a nonexistent capability rather than a competing tool such as list_segments, so the agent is left without a redirect.

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