Skip to main content
Glama
phxdev1

People Data Labs MCP Server

bulk_person_enrich

Enrich multiple person profiles simultaneously with bulk requests, streamlining data enhancement for person profiles using People Data Labs' comprehensive datasets and search capabilities.

Instructions

Enrich multiple person profiles in a single request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestsYesArray of person enrichment requests

Implementation Reference

  • The main handler function for the bulk_person_enrich tool. Validates input, calls the People Data Labs bulk person enrichment API endpoint, and returns the JSON response.
    private async handleBulkPersonEnrich(args: any) {
      if (!args || !Array.isArray(args.requests) || args.requests.length === 0) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Invalid bulk person enrichment parameters. Must provide an array of requests.'
        );
      }
    
      const response = await pdlApi.post('/person/bulk', args);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:194-217 (registration)
    Registers the bulk_person_enrich tool in the MCP server's tool list, including its description and input schema.
    {
      name: 'bulk_person_enrich',
      description: 'Enrich multiple person profiles in a single request',
      inputSchema: {
        type: 'object',
        properties: {
          requests: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                params: {
                  type: 'object',
                  description: 'Parameters for person enrichment',
                },
              },
              required: ['params'],
            },
            description: 'Array of person enrichment requests',
          },
        },
        required: ['requests'],
      },
    },
  • Defines the input schema for the bulk_person_enrich tool, specifying an array of requests each with params.
    inputSchema: {
      type: 'object',
      properties: {
        requests: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              params: {
                type: 'object',
                description: 'Parameters for person enrichment',
              },
            },
            required: ['params'],
          },
          description: 'Array of person enrichment requests',
        },
      },
      required: ['requests'],
    },
  • Dispatches calls to the bulk_person_enrich tool to the specific handler method.
    case 'bulk_person_enrich':
      return await this.handleBulkPersonEnrich(request.params.arguments);
  • Creates the axios instance used by the handler to make API calls to People Data Labs, including the API key from environment.
    const pdlApi = axios.create({
      baseURL: 'https://api.peopledatalabs.com/v5',
      headers: {
        'X-Api-Key': PDL_API_KEY,
        'Content-Type': 'application/json',
        'Accept': 'application/json',
      },
    });
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 this is for enrichment but doesn't disclose what enrichment entails, whether it's read-only or creates/modifies data, rate limits, authentication requirements, or what happens when requests fail partially. The description is too minimal for a mutation-like operation.

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 single sentence with zero waste. Every word contributes to the core purpose. The description is front-loaded with the essential action and scope.

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 tool with no annotations, no output schema, and potentially complex enrichment behavior, the description is inadequate. It doesn't explain what enrichment means, what data is returned, error handling for bulk operations, or how this differs from individual enrichment. The minimal description leaves too many questions unanswered.

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 the single 'requests' parameter with its structure. The description adds no additional parameter information beyond implying bulk processing through 'multiple person profiles', which aligns with the array structure but doesn't provide format examples or constraints.

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 verb ('enrich') and resource ('multiple person profiles') with the scope 'in a single request'. It distinguishes from the sibling 'enrich_person' by specifying bulk/multiple operations, but doesn't fully differentiate from other enrichment/search tools in terms of use case.

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 on when to use this tool versus alternatives like 'enrich_person' or search tools. The description implies batch processing but doesn't specify scenarios where bulk enrichment is preferred over individual enrichment or when search tools might be more appropriate.

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

Related 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/phxdev1/peopledatalabs-mcp'

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