Skip to main content
Glama
adamanz

Apollo.io MCP Server

by adamanz

people_search

Find professionals by organization domains, job titles, and seniority levels to identify potential contacts for business development, recruitment, or networking purposes.

Instructions

Use the People Search endpoint to find people

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
q_organization_domains_listNoList of organization domains to search within
person_titlesNoList of job titles to search for
person_senioritiesNoList of seniority levels to search for

Implementation Reference

  • Core handler function that executes the people_search tool logic by calling the Apollo.io People Search API endpoint.
     * Use the People Search endpoint to find people.
     * https://docs.apollo.io/reference/people-search
     */
    async peopleSearch(query: PeopleSearchQuery): Promise<any> {
      try {
        const url = `${this.baseUrl}/mixed_people/search`;
        const response = await this.axiosInstance.post(url, query);
        
        if (response.status === 200) {
          return response.data;
        } else {
          console.error(`Error: ${response.status} - ${response.statusText}`);
          return null;
        }
      } catch (error: any) {
        console.error(`Error: ${error.response?.status} - ${error.response?.statusText || error.message}`);
        return null;
      }
    }
  • TypeScript interface defining the input parameters for the peopleSearch query.
    export interface PeopleSearchQuery {
      q_organization_domains_list?: string[];
      person_titles?: string[];
      person_seniorities?: string[];
      [key: string]: any;
    }
  • src/index.ts:129-152 (registration)
    MCP tool registration defining the 'people_search' tool name, description, and input schema.
    {
      name: 'people_search',
      description: 'Use the People Search endpoint to find people',
      inputSchema: {
        type: 'object',
        properties: {
          q_organization_domains_list: { 
            type: 'array', 
            items: { type: 'string' },
            description: 'List of organization domains to search within' 
          },
          person_titles: { 
            type: 'array', 
            items: { type: 'string' },
            description: 'List of job titles to search for' 
          },
          person_seniorities: { 
            type: 'array', 
            items: { type: 'string' },
            description: 'List of seniority levels to search for' 
          }
        }
      }
    },
  • MCP server request handler that dispatches to the ApolloClient peopleSearch method and returns formatted response.
    case 'people_search': {
      const result = await this.apollo.peopleSearch(args);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'find[s] people' without disclosing behavioral traits such as search scope, result limits, authentication needs, or rate limits. It lacks details on what the tool actually returns or how it behaves operationally.

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 with no wasted words. It's front-loaded and to the point, though it could benefit from more detail given the lack of annotations and output schema.

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 no annotations, no output schema, and a vague description, the tool definition is incomplete. It doesn't explain what 'find[s] people' entails in terms of results, format, or limitations, leaving significant gaps for a search tool with three parameters.

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 parameters are documented in the schema. The description adds no meaning beyond the schema, as it doesn't explain parameter usage, interactions, or examples. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description states the tool 'find[s] people' which gives a vague purpose without specifying how it differs from sibling tools like 'people_enrichment' or 'organization_search'. It mentions the endpoint name but doesn't clarify the specific verb-resource combination beyond basic searching.

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 like 'people_enrichment' or 'organization_search'. The description only states what it does without context, prerequisites, or exclusions, leaving the agent to guess based on tool names alone.

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

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