Skip to main content
Glama
luiso2

Evolution API WhatsApp MCP Server

by luiso2

list_contacts

Retrieve all WhatsApp Business contacts for a specified instance to manage messaging and communication workflows.

Instructions

List all contacts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNameYesInstance name

Implementation Reference

  • The main handler function for the 'list_contacts' tool. It fetches contacts from the EvolutionAPI service for the given instance and returns them as a JSON-formatted text content block.
    private async handleListContacts(args: any) {
      const contacts = await evolutionAPI.findContacts(args.instanceName);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(contacts, null, 2)
          }
        ]
      };
    }
  • Defines the tool schema for 'list_contacts', specifying the input schema that requires an 'instanceName' parameter.
    {
      name: 'list_contacts',
      description: 'List all contacts',
      inputSchema: {
        type: 'object',
        properties: {
          instanceName: { type: 'string', description: 'Instance name' }
        },
        required: ['instanceName']
      }
    },
  • src/index.ts:524-525 (registration)
    Registers the 'list_contacts' tool in the switch statement within the CallToolRequest handler, dispatching to the specific handler method.
    case 'list_contacts':
      return await this.handleListContacts(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all contacts' implies a read-only operation, but it doesn't specify whether this is paginated, what the output format is, if there are rate limits, or any authentication requirements. This leaves significant gaps for a tool with no annotation coverage.

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?

The description 'List all contacts' is extremely concise—three words that directly convey the core action. It's front-loaded with no wasted words, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'contacts' entails, the return format, or behavioral aspects like pagination. For a tool with no structured support, more context is needed to guide effective use.

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 input schema has 100% description coverage, with 'instanceName' documented as 'Instance name'. The description adds no additional meaning about this parameter, such as what an instance represents or how it affects the listing. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all contacts' clearly states the verb ('List') and resource ('contacts'), making the basic purpose understandable. However, it lacks specificity about what 'all' means (e.g., scope, filters) and doesn't distinguish from potential sibling tools like 'get_chats' or 'get_messages' that might involve contact-related data, leaving it somewhat vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an 'instanceName'), exclusions, or comparisons to sibling tools like 'list_groups' or 'get_chats', leaving the agent to infer usage from the name alone.

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/luiso2/mcp-evolution-api'

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