Skip to main content
Glama
Aleksey-Panf

b2b-enrichment-mcp

bulk_enrich_people

Enrich up to 10 people in a single API call using Apollo data. Provide names and domain or email for batch enrichment.

Instructions

[Apollo] Enrich up to 10 people in a single API call.

Best for: enriching a batch of contacts at once — faster than looping over enrich_person and uses the same total credits (1 per matched person). Works on free Apollo plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
peopleYesList of people to enrich — maximum 10 per call. Each person needs: first_name + last_name + domain (or organization_name), OR just an email address.
reveal_personal_emailsNoIf True, attempt to return personal email addresses for all people. Requires a paid Apollo plan.
Behavior3/5

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

No annotations provided, so description is the sole source. Mentions batch limit and credit cost, but lacks disclosure on what enrichment entails or what happens on failure. Adequate but not rich.

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?

Extremely concise: two sentences plus a bullet point. Front-loaded with primary action and value. No wasted words.

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

Completeness4/5

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

For a simple batch enrichment tool with good schema, the description is sufficient. Lacks output description but no output schema exists, so not required. Slightly above baseline for context.

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 coverage is 100% and schema descriptions are detailed. The description adds minimal extra value (e.g., credit info). Baseline 3 for full coverage.

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?

The description clearly states the verb 'enrich' and the resource 'up to 10 people', and distinguishes itself from sibling tool 'enrich_person' by highlighting batching and same credit cost.

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

Usage Guidelines5/5

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

Explicitly states 'Best for: enriching a batch of contacts at once' and contrasts with 'enrich_person', also notes 'Works on free Apollo plan'.

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/Aleksey-Panf/b2b-enrichment-mcp'

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