Skip to main content
Glama
thevgergroup

apollo-io-mcp

by thevgergroup

Bulk Enrich People

apollo_bulk_enrich_people

Enrich multiple people records in bulk by matching via email, LinkedIn URL, name, or company to add missing data from Apollo's B2B database.

Instructions

Bulk enrich multiple people using Apollo match. Provide an array of people with email, linkedin_url, name, or company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
peopleYes
reveal_personal_emailsNoReveal personal emails (default: false)
reveal_phone_numberNoReveal phone numbers (default: false)
Behavior2/5

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

No annotations provided, so description carries full burden. 'Enrich' is vague; no mention of what data is added/overwritten, whether operation is idempotent, impact on existing data, or permissions needed.

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?

Two sentences, no redundancy. Front-loads the core action and input requirements.

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?

No output schema, no mention of return values or success criteria. For a bulk operation, should specify what enrichment results look like.

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 covers 67% of parameters with descriptions. Description adds that people array should contain objects with specified fields, but does not elaborate on format or validation beyond schema.

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

Purpose5/5

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

Clearly states 'bulk enrich multiple people' and specifies input fields (email, linkedin_url, name, or company). Distinguishes from sibling tools like apollo_enrich_person (single) and apollo_bulk_enrich_organizations (different resource).

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?

Implies use for bulk enrichment of people, but does not explicitly state when to use vs alternatives like single-person enrichment or when not to use. No exclusion criteria.

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

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