Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

get_lists

Retrieve all contact lists from your Apollo.io account to access and manage collections of saved sales prospects for outreach and analysis.

Instructions

Get all contact lists in your Apollo account. Lists are collections of saved contacts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number

Implementation Reference

  • The main handler function for the 'get_lists' tool. It makes an API call to Apollo's /contact_lists endpoint, processes the response, and formats a text summary of all contact lists including ID, name, contact count, and creation date.
    private async getLists(args: any) {
      const response = await this.axiosInstance.get("/contact_lists", {
        params: args,
      });
      const lists = response.data.contact_lists || [];
    
      let result = `Contact Lists (${lists.length}):\n\n`;
    
      lists.forEach((list: any, index: number) => {
        result += `${index + 1}. ${list.name}\n`;
        result += `   ID: ${list.id}\n`;
        result += `   Contacts: ${list.num_contacts || 0}\n`;
        result += `   Created: ${list.created_at ? new Date(list.created_at).toLocaleDateString() : "N/A"}\n\n`;
      });
    
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • src/index.ts:390-403 (registration)
    Tool registration in the getTools() method's return array. Defines the tool name, description, and input schema for pagination.
    {
      name: "get_lists",
      description:
        "Get all contact lists in your Apollo account. Lists are collections of saved contacts.",
      inputSchema: {
        type: "object",
        properties: {
          page: {
            type: "number",
            description: "Page number",
          },
        },
      },
    },
  • Input schema definition for the get_lists tool, specifying optional page parameter for pagination.
    inputSchema: {
      type: "object",
      properties: {
        page: {
          type: "number",
          description: "Page number",
        },
      },
    },
  • Dispatch case in the tool request handler that routes 'get_lists' calls to the getLists method.
    case "get_lists":
      return await this.getLists(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. It states the tool retrieves 'all contact lists' but does not mention pagination behavior (despite a 'page' parameter in the schema), rate limits, authentication needs, or what happens if no lists exist. For a read operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 is concise and front-loaded, consisting of two clear sentences: the first states the core purpose, and the second provides helpful context about what lists are. There is no wasted text, and every sentence earns its place by adding value.

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 the tool's low complexity (1 parameter, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavioral aspects like pagination or error handling. Without annotations or an output schema, more context would improve completeness, but it meets the basic threshold for a simple read operation.

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 the 'page' parameter documented as 'Page number.' The description does not add any meaning beyond this, such as explaining pagination defaults or constraints. With high schema coverage, the baseline score is 3, as the schema handles parameter documentation adequately.

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 clearly states the tool's purpose: 'Get all contact lists in your Apollo account.' It specifies the verb ('Get') and resource ('contact lists'), and adds clarifying context that 'Lists are collections of saved contacts.' However, it does not explicitly differentiate from sibling tools like 'get_list_contacts' or 'analyze_list,' which reduces it from a perfect score.

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 does not mention sibling tools like 'get_list_contacts' (which might retrieve contacts within a specific list) or 'analyze_list' (which might analyze list data), nor does it specify prerequisites or exclusions. Usage is implied but not explicitly stated.

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/masridigital/apollo.io-mcp'

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