Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

list_sequences

Retrieve all automated email campaigns from your Apollo account to manage outreach workflows and track campaign status.

Instructions

List all email sequences in your Apollo account. Sequences are automated email campaigns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number

Implementation Reference

  • The handler function for 'list_sequences' tool. Fetches email sequences (campaigns) from Apollo.io API endpoint '/emailer_campaigns', formats a human-readable list including name, ID, status, number of steps, and creation date, and returns it as MCP text content.
    private async listSequences(args: any) {
      const response = await this.axiosInstance.get("/emailer_campaigns", {
        params: args,
      });
      const sequences = response.data.emailer_campaigns || [];
    
      let result = `Email Sequences (${sequences.length}):\n\n`;
    
      sequences.forEach((seq: any, index: number) => {
        result += `${index + 1}. ${seq.name}\n`;
        result += `   ID: ${seq.id}\n`;
        result += `   Status: ${seq.active ? "Active" : "Inactive"}\n`;
        result += `   Contacts: ${seq.num_steps || 0} steps\n`;
        result += `   Created: ${seq.created_at ? new Date(seq.created_at).toLocaleDateString() : "N/A"}\n\n`;
      });
    
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
  • Input schema definition for the 'list_sequences' tool, allowing optional 'page' parameter for pagination.
    inputSchema: {
      type: "object",
      properties: {
        page: {
          type: "number",
          description: "Page number",
        },
      },
    },
  • src/index.ts:298-309 (registration)
    Registration of the 'list_sequences' tool in the getTools() method, including name, description, and input schema for the MCP server.
    name: "list_sequences",
    description:
      "List all email sequences in your Apollo account. Sequences are automated email campaigns.",
    inputSchema: {
      type: "object",
      properties: {
        page: {
          type: "number",
          description: "Page number",
        },
      },
    },
  • src/index.ts:72-73 (registration)
    Dispatch case in the main tool handler switch statement that routes 'list_sequences' calls to the listSequences implementation.
    case "list_sequences":
      return await this.listSequences(args);
Behavior2/5

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

With no annotations, the description carries full burden but lacks behavioral details. It doesn't disclose pagination behavior (implied by 'page' parameter), rate limits, authentication needs, or what data is returned. The phrase 'List all' suggests comprehensive retrieval but offers no further operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded, with two clear sentences. It efficiently conveys the core purpose without unnecessary elaboration, though it could be more structured with usage hints.

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?

For a tool with no annotations and no output schema, the description is incomplete. It lacks details on return format, pagination behavior, error handling, or how it fits into the broader context of sibling tools, leaving significant gaps for an AI agent.

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 the schema already documents the 'page' parameter. The description adds no parameter-specific information beyond implying pagination through 'List all,' which aligns with the schema but doesn't provide extra semantics like default values or format details.

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 verb ('List') and resource ('all email sequences in your Apollo account'), with additional context that sequences are 'automated email campaigns.' It distinguishes from siblings like 'get_sequence' (singular) but doesn't explicitly differentiate from other list-related tools like 'get_lists'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, compare to siblings like 'get_sequence' or 'analyze_sequence,' or specify use cases beyond the basic purpose.

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