Search People by Criteria · People Data Labs

Describe the people you want to find using a supported query or SQL. Search People Data Labs for a batch of matching profiles, then ask your Agent to organize the available names, profile IDs and details into a review list.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use Toolmu find-people-people-data-labs (223f7c59-e6fd-475e-9b47-ec4bedcb6aea). Reuse my connection or follow https://toolmu.com/SKILL.md. Read get_tool for current availability and price; honor my existing authority and budget. Convert my criteria to query or sql, never both. Use my batch size, one supported dataset and any requested data_include fields. Show the batch, total match count and available names, PDL IDs and details; retain missing values. Separately organize a review list. Another batch needs the same query and returned token, within my task scope and budget.

Task:
Find [up to 10 software engineers] at [Stripe]. Show each person’s name and available job details, then stop after this list.

Paste into your connected AI's conversation.

Connection guide

Up to 36 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

People Data Labs

Search People by Criteria · People Data Labs

You receive

Get a batch of matching people profiles for your criteria, a total match count and a continuation bookmark when supplied. Available names, PDL IDs and profile details help you distinguish entries. Your Agent can separately arrange the returned batch into a comparison table or shortlist, keeping the original criteria and missing values.

Start with your task

Find [up to 10 software engineers] at [Stripe]. Show each person’s name and available job details, then stop after this list.

What to know

A match does not verify a person's identity, current employment or usable contact information. Details depend on the selected dataset and available profile data. One batch does not contain every match.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
People search request`body`	`object`	Optional	Request settings containing either query or sql, together with any batch, dataset, field-selection or continuation settings. Use one query form per request.
Maximum profiles in this batch`body.size`anyOf · 1	`integer`	—	Integer from 1 to 100; default 1. Sets the maximum number of matching profiles returned in this batch, not the total number of matches. Default `1` Minimum `1` Maximum `100`
Structured people criteria`body.query`anyOf · 1	`object`	—	Elasticsearch query object using supported person fields and query operations. Supply this or sql, never both. Field names and values should follow the PDL person mapping.
Indent the response`body.pretty`anyOf · 1	`boolean`	—	Boolean, default false. Set true to request readable indentation of the response; it does not change matching criteria. Default `false`
Dataset to search`body.dataset`anyOf · 1	`string`	—	Choose one value: all, resume, email, phone, mobile_phone, street_address, consumer_social or developer. Default all. The choice sets the search dataset; it does not guarantee corresponding details in every profile. Default `all` Options `all, resume, email, phone, mobile_phone, street_address, consumer_social, developer`
Use title case in returned text`body.titlecase`anyOf · 1	`boolean`	—	Boolean, default false. Set true to request title-case presentation of returned text rather than its default lowercase form. Default `false`
Profile fields to include`body.data_include`anyOf · 1	`string`	—	Comma-separated supported person field names to include in the response, such as full_name. Select useful details without assuming that values are available.
Bookmark for the next batch`body.scroll_token`anyOf · 1	`string`	—	String bookmark from the preceding response. Use it with the same query to request the next batch; it is not a page number. Omit it for the first batch.
SQL people criteria`body.sql`anyOf · 2	`string`	—	SQL string of the form SELECT * FROM person WHERE ... using supported person fields. Supply this instead of query. Use size for the batch limit; SQL LIMIT and selected columns are ignored.
Maximum profiles in this batch`body.size`anyOf · 2	`integer`	—	Integer from 1 to 100; default 1. Sets the maximum number of matching profiles returned in this batch, not the total number of matches. Default `1` Minimum `1` Maximum `100`
Indent the response`body.pretty`anyOf · 2	`boolean`	—	Boolean, default false. Set true to request readable indentation of the response; it does not change matching criteria. Default `false`
Dataset to search`body.dataset`anyOf · 2	`string`	—	Choose one value: all, resume, email, phone, mobile_phone, street_address, consumer_social or developer. Default all. The choice sets the search dataset; it does not guarantee corresponding details in every profile. Default `all` Options `all, resume, email, phone, mobile_phone, street_address, consumer_social, developer`
Use title case in returned text`body.titlecase`anyOf · 2	`boolean`	—	Boolean, default false. Set true to request title-case presentation of returned text rather than its default lowercase form. Default `false`
Profile fields to include`body.data_include`anyOf · 2	`string`	—	Comma-separated supported person field names to include in the response, such as full_name. Select useful details without assuming that values are available.
Bookmark for the next batch`body.scroll_token`anyOf · 2	`string`	—	String bookmark from the preceding response. Use it with the same query to request the next batch; it is not a page number. Omit it for the first batch.

View raw JSON

{
  "type": "object",
  "required": [],
  "properties": {
    "body": {
      "anyOf": [
        {
          "type": "object",
          "required": [
            "query"
          ],
          "properties": {
            "size": {
              "type": "integer",
              "default": 1,
              "maximum": 100,
              "minimum": 1
            },
            "query": {
              "type": "object",
              "propertyNames": {
                "type": "string"
              },
              "additionalProperties": {}
            },
            "pretty": {
              "type": "boolean",
              "default": false
            },
            "dataset": {
              "enum": [
                "all",
                "resume",
                "email",
                "phone",
                "mobile_phone",
                "street_address",
                "consumer_social",
                "developer"
              ],
              "type": "string",
              "default": "all"
            },
            "titlecase": {
              "type": "boolean",
              "default": false
            },
            "data_include": {
              "type": "string"
            },
            "scroll_token": {
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        {
          "type": "object",
          "required": [
            "sql"
          ],
          "properties": {
            "sql": {
              "type": "string"
            },
            "size": {
              "type": "integer",
              "default": 1,
              "maximum": 100,
              "minimum": 1
            },
            "pretty": {
              "type": "boolean",
              "default": false
            },
            "dataset": {
              "enum": [
                "all",
                "resume",
                "email",
                "phone",
                "mobile_phone",
                "street_address",
                "consumer_social",
                "developer"
              ],
              "type": "string",
              "default": "all"
            },
            "titlecase": {
              "type": "boolean",
              "default": false
            },
            "data_include": {
              "type": "string"
            },
            "scroll_token": {
              "type": "string"
            }
          },
          "additionalProperties": false
        }
      ],
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "~standard": {
        "vendor": "zod",
        "version": 1,
        "jsonSchema": {}
      }
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

Write conditions against People Data Labs person fields and their mapping. Searches run directly against those values without cleaning or preprocessing. The supported Elasticsearch query types are term, terms, exists, bool, match, range, match_phrase, wildcard, prefix and match_all. PDL excludes aggregations and custom scoring, and limits each query array to 1,000 elements.

SQL uses SELECT * FROM person WHERE ... and must translate to those supported query operations. PDL ignores selected columns and SQL LIMIT: use size for the batch limit and data_include for returned field selection. LIKE expressions using % are limited to 20 wildcard terms. When testing a structured field, use its actual subfield, such as experience.title.name, rather than the whole experience object.

Choose one dataset value from the input reference. Use data_include as a comma-separated list of supported person field names to narrow the profile details. The documented response uses data for the profile batch, total for all records matching the query and scroll_token for the next-batch bookmark. Unknown profile values are null; selected fields and dataset categories do not guarantee contact details.

Continue with the original query and the latest returned scroll_token. PDL describes a null or absent token as a possible completion signal; do not send null as the token input. Each next batch is another request, so stop at the scope you requested. pretty and titlecase change presentation, not profile accuracy or freshness.

People Data Labs: Person Search inputs

People Data Labs: Person Search response

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

The total covers all records matching the query, while size limits one returned batch to at most 1–100 profiles and defaults to 1. Read the batch count and total separately. A large total does not mean those profiles have already been retrieved.

Search People by Criteria · People Data Labs

Search People by Criteria · People Data Labs

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Say who you want to find

Choose how many to review first

Review the people before continuing

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Say who you want to find

Choose how many to review first

Review the people before continuing

Questions about this tool.

Why can the total match count exceed the number of profiles shown?

How do I request only the profile details needed for my review?

Does matching an employer condition prove that someone works there now?

How can my Agent continue without retrieving every match?