Provided by People Data Labs
List the Common Values of One Person Dataset Field by Prefix (PDL)
List the most common values of one PDL person field — job title, company, school, skill, role, sub-role, industry, major, class, website, location name, region, country or all locations — that begin with a typed prefix, each value with the number of person records carrying it. Pass a value back verbatim as a filter value in the PDL person and company search Endpoints. Up to 100 values per call; the field name comes from a fixed list.
How to run it
Step 1Set up
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.md
Show me how to use the People Data Labs endpoint /v5/autocomplete on Glasser.glasser run -p pdl -e '/v5/autocomplete' -i '{"size":5,"text":"data","field":"title"}' --endpoint-version 1Uses endpoint version 1. Inspect the current price before running. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"pdl","endpoint":"/v5/autocomplete","input":{"size":5,"text":"data","field":"title"},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Uses endpoint version 1; inspect the current price before running.
Step 2Try a specific example task
When you need to plan new content, you might organize keyword ideas into related topics to build a workable content plan.
Copy this prompt into your agent to group keyword ideas for your content plan.
Use pdl:/v5/autocomplete on Glasser.
Group the returned keywords into topics I can use to plan content.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"field"
],
"properties": {
"size": {
"type": "integer",
"maximum": 100,
"minimum": 1
},
"text": {
"type": "string",
"maxLength": 100
},
"field": {
"enum": [
"all_location",
"class",
"company",
"country",
"industry",
"location_name",
"major",
"region",
"role",
"school",
"sub_role",
"skill",
"title",
"website"
],
"type": "string"
}
},
"additionalProperties": false
}{
"size": 5,
"text": "data",
"field": "title"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How pricing works
| Data returned or no match | The same price with or without matching data. | $0.00 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |