Skip to main content
Glama
lkm1developer

Apollo.io MCP Server

get_person_email

Retrieve email addresses for individuals by providing their Apollo.io person ID, enabling contact information lookup through the Apollo.io data platform.

Instructions

Get email address for a person using their Apollo ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apollo_idYesApollo.io person ID

Implementation Reference

  • MCP tool handler for 'get_person_email' that delegates to ApolloClient.getPersonEmail and formats the response as JSON text content.
    case 'get_person_email': {
      const result = await this.apollo.getPersonEmail(args.apollo_id as string);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • src/index.ts:186-199 (registration)
    Registration of the 'get_person_email' tool in the list of available tools, including name, description, and input schema.
    {
      name: 'get_person_email',
      description: 'Get email address for a person using their Apollo ID',
      inputSchema: {
        type: 'object',
        properties: {
          apollo_id: {
            type: 'string',
            description: 'Apollo.io person ID'
          }
        },
        required: ['apollo_id']
      }
    },
  • Core implementation of getPersonEmail method in ApolloClient class that performs the API request to fetch email addresses using the person's Apollo ID.
    async getPersonEmail(apolloId: string): Promise<any> {
      try {
        if (!apolloId) {
          throw new Error('Apollo ID is required');
        }
    
        const baseUrl = `https://app.apollo.io/api/v1/mixed_people/add_to_my_prospects`;
        const payload = {
          entity_ids: [apolloId],
          analytics_context: 'Searcher: Individual Add Button',
          skip_fetching_people: true,
          cta_name: 'Access email',
          cacheKey: Date.now()
        };
    
        const response = await axios.post(baseUrl, payload, { 
          headers: { 
            'X-Api-Key': this.apiKey,
            'Content-Type': 'application/json'
          } 
        });
    
        if (!response.data) {
          throw new Error('No data received from Apollo API');
        }
    
        const emails = (response?.data?.contacts ?? []).map((item: any) => item.email);
        return emails;
      } catch (error: any) {
        console.error(`Error getting person email: ${error.message}`);
        return null;
      }
    }
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 'Get email address', which implies a read-only operation, but doesn't disclose any behavioral traits like authentication requirements, rate limits, error handling, or what happens if no email is found. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 a single, efficient sentence: 'Get email address for a person using their Apollo ID'. It is front-loaded with the core action and resource, with no wasted words. Every part of the sentence contributes directly to understanding the tool's purpose, making it highly concise and well-structured.

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 simple lookup with one parameter) and lack of annotations or output schema, the description is incomplete. It doesn't explain what the return value looks like (e.g., email string, error messages), behavioral aspects like permissions or limitations, or how it differs from sibling tools. For a tool with no structured data beyond the input schema, more context is needed to be fully helpful.

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 adds minimal meaning beyond the input schema. It mentions 'using their Apollo ID', which aligns with the 'apollo_id' parameter in the schema. Since schema description coverage is 100% (the parameter is fully described as 'Apollo.io person ID'), the baseline is 3. The description doesn't provide additional syntax, format details, or constraints, so it meets but doesn't exceed the baseline.

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 email address for a person using their Apollo ID'. It specifies the verb ('Get'), resource ('email address'), and key identifier ('Apollo ID'), making the action unambiguous. However, it does not explicitly differentiate this tool from sibling tools like 'people_enrichment' or 'people_search', which might also retrieve person-related data, so it doesn't fully distinguish from 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 sibling tools like 'people_enrichment' or 'people_search', nor does it specify prerequisites, such as needing an Apollo ID. The context is implied (use when you have an Apollo ID and want an email), but there's no explicit when/when-not or alternative recommendations.

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/lkm1developer/apollo-io-mcp-server'

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