Skip to main content
Glama
adamanz

Apollo.io MCP Server

by adamanz

organization_enrichment

Enrich company data by providing domain or name to retrieve comprehensive organizational information from Apollo.io.

Instructions

Use the Organization Enrichment endpoint to enrich data for 1 company

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoCompany domain
nameNoCompany name

Implementation Reference

  • Core handler function that executes the organization enrichment by calling Apollo.io API /organizations/enrich endpoint with query params.
    async organizationEnrichment(query: OrganizationEnrichmentQuery): Promise<any> {
      try {
        const url = `${this.baseUrl}/organizations/enrich`;
        const response = await this.axiosInstance.get(url, { params: 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 query for organization enrichment.
    export interface OrganizationEnrichmentQuery {
      domain?: string;
      name?: string;
      [key: string]: any;
    }
  • src/index.ts:112-128 (registration)
    Tool registration in MCP server, defining name, description, and input schema for listTools.
    {
      name: 'organization_enrichment',
      description: 'Use the Organization Enrichment endpoint to enrich data for 1 company',
      inputSchema: {
        type: 'object',
        properties: {
          domain: { 
            type: 'string', 
            description: 'Company domain' 
          },
          name: { 
            type: 'string', 
            description: 'Company name' 
          }
        }
      }
    },
  • MCP CallToolRequest handler case that invokes the ApolloClient organizationEnrichment method and formats response.
    case 'organization_enrichment': {
      const result = await this.apollo.organizationEnrichment(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?

No annotations are provided, so the description carries full burden. It states the tool 'enrich data' but doesn't disclose behavioral traits like whether it's a read-only operation, what data sources it uses, rate limits, authentication requirements, or what 'enrich' entails. The description is too minimal for a tool with no annotation coverage.

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 sentence with zero wasted words, making it appropriately concise. However, it lacks front-loading of critical information and could benefit from more structure to clarify the tool's value.

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 purpose, the description is incomplete. It doesn't explain what 'enrich' means, what data is returned, or how this tool fits among siblings. For a tool with 2 parameters and complex sibling relationships, more context is needed.

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 (domain and company name). The description adds no additional meaning about these parameters, such as whether both are required, their relationship, or examples. With high schema coverage, baseline 3 is appropriate.

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 'enrich data for 1 company', which provides a general purpose but lacks specificity. It doesn't clearly distinguish what 'enrich' means or how it differs from sibling tools like organization_search or people_enrichment. The purpose is vague rather than tautological.

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 organization_search or people_enrichment. The description mentions it's for '1 company' but doesn't specify use cases, prerequisites, or exclusions. Without any contextual direction, the agent must infer usage.

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