Skip to main content
Glama
adamanz

Apollo.io MCP Server

by adamanz

organization_search

Search for organizations by domain or location to identify and connect with potential business partners or clients.

Instructions

Use the Organization Search endpoint to find organizations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
q_organization_domains_listNoList of organization domains to search for
organization_locationsNoList of organization locations to search for

Implementation Reference

  • src/index.ts:153-171 (registration)
    Tool registration in the list of available tools, including name, description, and JSON input schema.
    {
      name: 'organization_search',
      description: 'Use the Organization Search endpoint to find organizations',
      inputSchema: {
        type: 'object',
        properties: {
          q_organization_domains_list: { 
            type: 'array', 
            items: { type: 'string' },
            description: 'List of organization domains to search for' 
          },
          organization_locations: { 
            type: 'array', 
            items: { type: 'string' },
            description: 'List of organization locations to search for' 
          }
        }
      }
    },
  • MCP tool handler switch case that calls the ApolloClient organizationSearch method and formats the result as text content.
    case 'organization_search': {
      const result = await this.apollo.organizationSearch(args);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      };
    }
  • TypeScript interface defining the input parameters for the organizationSearch query.
    export interface OrganizationSearchQuery {
      q_organization_domains_list?: string[];
      organization_locations?: string[];
      [key: string]: any;
    }
  • Helper method in ApolloClient class that performs the HTTP POST request to Apollo.io's organization search endpoint.
    async organizationSearch(query: OrganizationSearchQuery): Promise<any> {
      try {
        const url = `${this.baseUrl}/mixed_companies/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;
      }
    }
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 offers minimal behavioral insight. It doesn't disclose whether this is a read-only operation, what authentication might be needed, rate limits, or what the search returns (e.g., partial matches, exact matches). The phrase 'find organizations' implies a query operation but lacks detail.

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 with the core purpose, though it could be more informative. The brevity is appropriate but borders on under-specification.

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?

For a search tool with 2 parameters and no annotations or output schema, the description is incomplete. It doesn't explain what the search returns, how results are filtered, or any limitations. Given the complexity and lack of structured data, more context is needed for effective use.

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 the schema already documents both parameters fully. The description adds no meaning beyond what the schema provides—it doesn't explain how the parameters interact (e.g., AND/OR logic) or provide examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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's purpose as 'find organizations' which is clear but vague. It specifies the endpoint name but doesn't differentiate from sibling tools like 'organization_enrichment' or 'people_search'. The verb 'find' is generic rather than specific about the search mechanism.

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. The description doesn't mention sibling tools like 'organization_enrichment' or 'people_search', nor does it specify appropriate contexts or exclusions for using this search endpoint.

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