Skip to main content
Glama

People Data Labs MCP by usefulapi

Enrich a person

pdl_person_enrich
Read-only

Find the single best-matching person profile for a set of identifying attributes (name, email, phone, profile URL, company, etc.). Returns one record plus a likelihood score (1-10), or a 404 'no match' body. Use uniquely-identifying inputs for best results. API: GET /person/enrich.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lidNoLinkedIn numerical ID.
nameNoFull name, e.g. 'Sean Thorne'.
emailNoEmail address, or an array of email addresses.
phoneNoPhone number (E.164 or local).
pdl_idNoPDL persistent ID for a person record.
prettyNoPretty-print the JSON response.
regionNoState / region, e.g. 'california'.
schoolNoSchool name or website the person attended.
companyNoCompany name, website, or PDL company id the person works at.
countryNoCountry name, e.g. 'united states'.
profileNoSocial profile URL(s), e.g. a LinkedIn URL. String or array.
localityNoCity / locality, e.g. 'san francisco'.
locationNoFree-text location, e.g. 'San Francisco, CA, USA'.
requiredNoOnly return a match that contains these fields, e.g. 'emails AND mobile_phone'.
last_nameNoLast / family name.
titlecaseNoTitlecase the returned data (default false = lowercase).
birth_dateNoBirth date (yyyy or yyyy-mm-dd).
first_nameNoFirst / given name.
postal_codeNoPostal / ZIP code (assumed US if no country).
min_likelihoodNoOnly return a 200 if match confidence >= this (1-10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.