Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

add_to_sequence

Add contacts to Apollo.io email sequences using contact IDs or email addresses to automate outreach campaigns.

Instructions

Add contacts to a sequence. Provide sequence ID and contact email addresses or contact IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequence_idYesSequence ID
contact_idsNoArray of contact IDs to add
contact_emailsNoArray of contact emails to add
mailbox_idNoMailbox ID to send from (optional)

Implementation Reference

  • The primary handler function for the 'add_to_sequence' tool. It sends a POST request to Apollo's API endpoint to add specified contact IDs to the given sequence ID, optionally specifying a mailbox, and returns a success message.
    private async addToSequence(args: any) {
      const response = await this.axiosInstance.post(
        `/emailer_campaigns/${args.sequence_id}/add_contact_ids`,
        {
          contact_ids: args.contact_ids,
          emailer_campaign_id: args.sequence_id,
          send_email_from_email_account_id: args.mailbox_id,
        }
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Successfully added ${args.contact_ids?.length || args.contact_emails?.length || 0} contact(s) to sequence ${args.sequence_id}`,
          },
        ],
      };
    }
  • Input schema for the 'add_to_sequence' tool, defining required sequence_id and optional contact_ids, contact_emails, and mailbox_id.
    inputSchema: {
      type: "object",
      properties: {
        sequence_id: {
          type: "string",
          description: "Sequence ID",
        },
        contact_ids: {
          type: "array",
          items: { type: "string" },
          description: "Array of contact IDs to add",
        },
        contact_emails: {
          type: "array",
          items: { type: "string" },
          description: "Array of contact emails to add",
        },
        mailbox_id: {
          type: "string",
          description: "Mailbox ID to send from (optional)",
        },
      },
      required: ["sequence_id"],
    },
  • src/index.ts:341-369 (registration)
    Tool registration in the getTools() method's return array, specifying name, description, and input schema for listTools response.
    {
      name: "add_to_sequence",
      description:
        "Add contacts to a sequence. Provide sequence ID and contact email addresses or contact IDs.",
      inputSchema: {
        type: "object",
        properties: {
          sequence_id: {
            type: "string",
            description: "Sequence ID",
          },
          contact_ids: {
            type: "array",
            items: { type: "string" },
            description: "Array of contact IDs to add",
          },
          contact_emails: {
            type: "array",
            items: { type: "string" },
            description: "Array of contact emails to add",
          },
          mailbox_id: {
            type: "string",
            description: "Mailbox ID to send from (optional)",
          },
        },
        required: ["sequence_id"],
      },
    },
  • src/index.ts:78-79 (registration)
    Dispatch/registration of the tool handler in the central CallToolRequestSchema switch statement.
    case "add_to_sequence":
      return await this.addToSequence(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Add contacts') but fails to describe what this entails—e.g., whether it triggers emails, changes contact statuses, requires specific permissions, or has side effects like rate limits. This is inadequate for a mutation tool with zero 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 is a single, efficient sentence that front-loads the core purpose ('Add contacts to a sequence') and briefly specifies inputs. There is no wasted text, making it appropriately concise and well-structured for quick understanding.

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 tool's complexity (a mutation with 4 parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain the behavioral impact, return values, error conditions, or how it interacts with siblings like 'remove_from_sequence', 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?

The description mentions 'sequence ID and contact email addresses or contact IDs', which aligns with the schema parameters. Since schema description coverage is 100%, the schema already documents all parameters well, so the description adds minimal value beyond restating them. This meets the baseline for high schema coverage.

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 action ('Add contacts to a sequence') and specifies the target resource ('sequence'), which distinguishes it from siblings like 'create_contact' or 'update_contact'. However, it doesn't explicitly differentiate from 'remove_from_sequence' beyond the verb difference, missing a direct sibling comparison.

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 like 'create_contact' for new contacts or 'update_contact' for modifications. It mentions required inputs but offers no context about prerequisites, timing, or exclusions, leaving usage unclear.

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