Skip to main content
Glama

list_contacts

Retrieve a list of contacts with optional filters and select specific fields to minimize response size.

Instructions

List all contacts with optional filters for phone, mobile, or custom ID. Supports field filtering to reduce response size.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (optional)
limitNoMaximum number of items to return (default: 50, max: 500)
summaryNoReturn only count and pagination metadata without items (default: false)
phoneNoFilter by exact phone number match
mobileNoFilter by exact mobile number match
customIdNoFilter by custom ID(s)
fieldsNoSelect specific fields to return (e.g., ["id", "name", "email"]). Reduces response size by 70-90%. If not provided, returns default fields: id, customId, name, email
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions filtering capabilities and field size reduction but omits behavioral details like pagination behavior, rate limits, or error handling. It is adequate but not rich.

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 concise sentences that front-load the purpose. No wasted words; every sentence adds value. Perfect structure for a list tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, no output schema, and no annotations, the description is too brief. It does not mention pagination parameters (page, limit) or the summary option, which are important for usage. The schema covers these, but the description should provide a more complete overview.

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 description coverage is 100%, so baseline is 3. The description adds value by stating that field filtering reduces response size by 70-90% and listing filterable fields (phone, mobile, custom ID), which is not in the schema descriptions.

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?

The description clearly states the action (list), resource (contacts), and key features (filters for phone, mobile, custom ID; field filtering). It distinguishes from sibling tools like get_contact (single) and list_contact_groups (groups).

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 description implies usage for listing multiple contacts with filters but does not explicitly state when to use this tool over alternatives such as get_contact for a single contact or other list tools. No exclusions or contextual hints are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/iamsamuelfraga/mcp-holded'

If you have feedback or need assistance with the MCP directory API, please join our Discord server