Skip to main content
Glama

List contacts

list_contacts
Read-onlyIdempotent

List contacts, newest first. Filter by tag, segment_id, list_id, exact phone_number, or a free-text q (name, email, company).

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
qNoSearch text
tagNoOnly contacts with this tag
limitNoMax results (default 25, max 100)
cursorNonext_cursor from the previous page
list_idNoOnly contacts in this list
segment_idNoOnly contacts in this segment
phone_numberNoE.164

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / list_id / description
      Added value: +"Only contacts in this list"
    • addedInput schema / properties / segment_id / description
      Added value: +"Only contacts in this segment"
    • addedInput schema / properties / tag / description
      Added value: +"Only contacts with this tag"
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior not in annotations ('newest first' ordering), but says nothing about pagination behavior or result-size limits, which matter for a paged list tool.

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?

Two short sentences, zero waste, ordering stated up front and filters enumerated second. Every clause earns its place.

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 a fully documented 7-param schema and clear annotations, the description covers what matters: ordering and filter semantics. Only pagination expectations and the relationship to sibling query tools are missing.

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?

Schema coverage is 100% so baseline is 3; the description exceeds it by clarifying that 'q' is free-text across name, email and company, and that phone_number is an exact match — details the schema's terse 'Search text' does not convey. It omits limit/cursor from prose, which is acceptable since the schema documents them.

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 plus ordering ('newest first') and the filter surface, so an agent knows this is an unfiltered-by-default paged contact read. It doesn't explicitly contrast with siblings like query_audience or list_list_contacts, so sibling differentiation is only implicit.

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?

The filter list implies when to use each parameter, but there is no explicit guidance on when to choose this tool over query_audience or list_list_contacts, nor any note that all filters are optional and combining them is the intended pattern.

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.