Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

remove_from_sequence

Remove specific contacts from a sales sequence in Apollo.io by providing sequence and contact IDs to manage prospect lists.

Instructions

Remove contacts from a sequence. Provide sequence ID and contact IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequence_idYesSequence ID
contact_idsYesArray of contact IDs to remove

Implementation Reference

  • The primary handler function that executes the tool. It makes a POST request to the Apollo API endpoint `/emailer_campaigns/{sequence_id}/remove_contact_ids` with the contact_ids, ignores the response, and returns a formatted success message indicating the number of contacts removed.
    private async removeFromSequence(args: any) {
      const response = await this.axiosInstance.post(
        `/emailer_campaigns/${args.sequence_id}/remove_contact_ids`,
        {
          contact_ids: args.contact_ids,
        }
      );
    
      return {
        content: [
          {
            type: "text",
            text: `Successfully removed ${args.contact_ids.length} contact(s) from sequence ${args.sequence_id}`,
          },
        ],
      };
    }
  • The input schema defining the required parameters for the tool: sequence_id (string) and contact_ids (array of strings). Used for validation in the MCP tool call.
    inputSchema: {
      type: "object",
      properties: {
        sequence_id: {
          type: "string",
          description: "Sequence ID",
        },
        contact_ids: {
          type: "array",
          items: { type: "string" },
          description: "Array of contact IDs to remove",
        },
      },
      required: ["sequence_id", "contact_ids"],
    },
  • src/index.ts:370-389 (registration)
    The tool registration object returned by getTools(), including name, description, and inputSchema. This makes the tool available to the MCP server.
    {
      name: "remove_from_sequence",
      description:
        "Remove contacts from a sequence. Provide sequence ID and 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 remove",
          },
        },
        required: ["sequence_id", "contact_ids"],
      },
    },
  • src/index.ts:80-81 (registration)
    Switch case in the tool execution handler that dispatches calls to 'remove_from_sequence' to the corresponding method.
    case "remove_from_sequence":
      return await this.removeFromSequence(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 is a removal but does not clarify if this is destructive (e.g., permanent deletion or reversible), what permissions are required, or how the operation affects the sequence or contacts. 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 extremely concise with two sentences that directly state the tool's purpose and parameters without any wasted words. It is front-loaded and efficiently communicates the essential information in a minimal format.

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 for a mutation tool. It does not address behavioral aspects like safety, permissions, or response format, which are critical for proper tool invocation. The high schema coverage helps with parameters but does not compensate for other gaps.

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 the parameters ('sequence ID and contact IDs'), but with 100% schema description coverage, the input schema already fully documents these parameters. The description adds no additional meaning, such as format examples or constraints, beyond what the schema provides, meeting the baseline for high 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 ('Remove contacts from a sequence') and specifies the resource ('sequence'), making the purpose understandable. However, it does not explicitly differentiate this tool from its sibling 'add_to_sequence' beyond the opposite action, missing a direct comparison that would enhance clarity.

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, such as 'add_to_sequence' or other contact management tools. It lacks context about prerequisites, scenarios for removal, or any exclusions, leaving usage entirely implicit.

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