Skip to main content
Glama
masridigital

Apollo.io MCP Server

by masridigital

get_sequence

Retrieve detailed information about Apollo.io email sequences, including steps, performance statistics, and configuration settings for sales outreach management.

Instructions

Get detailed information about a specific sequence including steps, stats, and settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSequence ID

Implementation Reference

  • The main handler function for the 'get_sequence' tool. It makes an API call to retrieve the specific sequence by ID from Apollo's emailer_campaigns endpoint, formats the details including name, status, creation date, number of steps, and lists each step with type, wait time, and subject.
    private async getSequence(args: any) {
      const response = await this.axiosInstance.get(`/emailer_campaigns/${args.id}`);
      const seq = response.data.emailer_campaign;
    
      let result = `Sequence Details:\n\n`;
      result += `Name: ${seq.name}\n`;
      result += `ID: ${seq.id}\n`;
      result += `Status: ${seq.active ? "Active" : "Inactive"}\n`;
      result += `Created: ${seq.created_at ? new Date(seq.created_at).toLocaleDateString() : "N/A"}\n`;
      result += `Steps: ${seq.num_steps || 0}\n\n`;
    
      if (seq.emailer_steps && seq.emailer_steps.length > 0) {
        result += `Sequence Steps:\n`;
        seq.emailer_steps.forEach((step: any, index: number) => {
          result += `\nStep ${index + 1}:\n`;
          result += `  Type: ${step.type || "Email"}\n`;
          result += `  Wait: ${step.wait_time || 0} days\n`;
          result += `  Subject: ${step.subject || "N/A"}\n`;
        });
      }
    
      return {
        content: [
          {
            type: "text",
            text: result,
          },
        ],
      };
    }
  • src/index.ts:311-325 (registration)
    The tool registration in the getTools() array, including name, description, and input schema requiring a 'sequence ID'.
    {
      name: "get_sequence",
      description:
        "Get detailed information about a specific sequence including steps, stats, and settings.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "Sequence ID",
          },
        },
        required: ["id"],
      },
    },
  • The input schema definition for the 'get_sequence' tool, specifying that it requires an object with a mandatory 'id' string parameter representing the Sequence ID.
    inputSchema: {
      type: "object",
      properties: {
        id: {
          type: "string",
          description: "Sequence ID",
        },
      },
      required: ["id"],
    },
  • src/index.ts:74-75 (registration)
    The switch case in the CallToolRequestHandler that routes calls to the 'get_sequence' handler function.
    case "get_sequence":
      return await this.getSequence(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 this is a 'Get' operation, implying read-only behavior, but doesn't specify whether it requires authentication, has rate limits, returns paginated results, or handles errors. The description adds minimal behavioral context beyond the basic operation.

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 a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words and directly states what the tool does. However, it could be slightly more structured by explicitly mentioning the parameter or output, but it earns its place without waste.

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 has no annotations, no output schema, and a simple parameter, the description is incomplete. It doesn't explain what 'detailed information' includes, how to interpret the output, or any behavioral traits like error handling. For a tool that retrieves data, more context on the response format and usage constraints would be beneficial.

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 'id' parameter documented as 'Sequence ID'. The description doesn't add any meaning beyond this, such as format examples or where to find the ID. 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.

Purpose4/5

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

The description clearly states the verb 'Get' and the resource 'detailed information about a specific sequence', including specific attributes like 'steps, stats, and settings'. It distinguishes from siblings like 'list_sequences' (which lists sequences) and 'analyze_sequence' (which might analyze rather than retrieve details), though it doesn't explicitly name alternatives.

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, such as needing a sequence ID, or differentiate from similar tools like 'analyze_sequence' or 'get_list_contacts'. Usage is implied by the purpose but lacks explicit context or exclusions.

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