Skip to main content
Glama
FromSmall2Big

Apollo.io MCP Server

bulk_enrich_organizations

Enrich multiple company profiles simultaneously using domain names to obtain comprehensive organization data for sales and marketing activities.

Instructions

Bulk enrich multiple organizations at once.

This tool enriches multiple companies simultaneously based on their domains. Up to 10 domains can be processed in a single request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'bulk_enrich_organizations' MCP tool. It is decorated with @mcp.tool() for automatic registration with FastMCP. The function performs bulk organization enrichment by sending a POST request to Apollo.io's bulk_enrich endpoint with a list of up to 10 domains, handling validation and errors.
    @mcp.tool()
    async def bulk_enrich_organizations(domains: List[str]) -> Dict[str, Any]:
        """
        Bulk enrich multiple organizations at once.
        
        This tool enriches multiple companies simultaneously based on their domains.
        Up to 10 domains can be processed in a single request.
        """
        if len(domains) > 10:
            return {"error": "Maximum 10 domains allowed per bulk enrichment request"}
        
        endpoint = "/api/v1/organizations/bulk_enrich"
        data = {"domains": domains}
        
        try:
            result = await apollo_client.make_request("POST", endpoint, data=data)
            return result
        except httpx.HTTPStatusError as e:
            return {"error": f"API request failed: {e.response.status_code} {e.response.text}"}
        except Exception as e:
            return {"error": f"Request failed: {str(e)}"}
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 mentions the batch limit (10 domains) but lacks details on permissions, rate limits, what 'enrich' entails (e.g., data sources, fields added), error handling, or response format. For a mutation tool with zero annotation coverage, this is insufficient.

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 front-loaded with the core purpose in the first sentence, followed by a clarifying detail. Both sentences are essential—no wasted words. It's appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 1 parameter with 0% schema coverage, an output schema exists (so return values are covered), and no annotations, the description is minimally adequate. It covers the batch nature and limit but misses behavioral aspects like mutation effects or error cases. For a bulk operation tool, more context on outcomes would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It clarifies that 'domains' are used for enrichment and specifies a limit of 10 items, adding some meaning. However, it doesn't explain domain format requirements (e.g., valid TLDs), whether duplicates are allowed, or other constraints, leaving gaps in parameter understanding.

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: 'Bulk enrich multiple organizations at once' and specifies it's based on domains. It distinguishes from the sibling 'enrich_organization' by emphasizing bulk capability. However, it doesn't explicitly contrast with other siblings like 'enrich_person' or 'search_accounts'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by stating 'Up to 10 domains can be processed in a single request,' suggesting this tool is for batch processing. It doesn't explicitly state when to use this versus 'enrich_organization' (single vs. bulk) or other alternatives, nor does it provide exclusion criteria or prerequisites.

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/FromSmall2Big/Apollo-MCP'

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