Skip to main content
Glama

ZOOQ - LinkedIn Data for AI Agents

search_people

Read-onlyIdempotent

Search professional records with rich filters — name, title, company, skills, education, tenure, geography. Cursor-paginated. (Costs 10 Zooq credits.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per page, 1-50 (default 20).
titleNoJob-title match (min 3 chars).
cursorNoOpaque pagination cursor; omit for the first page.
degreeNoDegree filter.
skillsNoComma-separated normalized skill names. Resolve via /g/title-skills-lookup.
summaryNoFree-text summary/about match (min 3 chars).
geo_cityNoCity name (min 3 chars).
headlineNoFree-text headline match (min 3 chars).
last_nameNoLast name (min 3 chars).
first_nameNoFirst name (min 3 chars).
is_creatorNoOnly content creators.
is_premiumNoOnly premium members.
current_onlyNoRestrict title/company matches to current positions.
is_boomerangNoOnly people who rejoined a former employer.
skills_matchNoSkill match mode. Accepted values: any (default), all.
certificationsNoCertification name filter.
field_of_studyNoField-of-study filter.
education_levelNoEducation level filter.
institution_idsNoComma-separated institution ids (inst_...). Resolve via /search/schools.
skill_count_maxNoMaximum number of listed skills.
skill_count_minNoMinimum number of listed skills.
speaks_languageNoSpoken-language filter.
geo_country_codeNoISO country code.
last_change_typeNoJob-change type. Accepted values: joined, left, title_change.
primary_languageNoProfile primary language code, e.g. en.
tenure_max_yearsNoMaximum tenure in current role (years).
tenure_min_yearsNoMinimum tenure in current role (years).
company_count_maxNoMaximum number of companies in history.
company_count_minNoMinimum number of companies in history.
organization_slugsNoComma-separated company slugs — the part after linkedin.com/company/. Company URLs and org_ ids (from companies_info / search_companies) are accepted and translated. Combine with current_only=true for people who work there NOW.
certification_authorityNoCertification issuing authority filter.
last_change_within_daysNoOnly people with a job change in the last N days.
current_company_count_minNoMinimum number of concurrent current companies.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoArray in the example

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds genuinely useful behavioral context beyond annotations: cursor-based pagination and a 10-Zooq-credit cost, which are not visible in the schema or annotations.

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?

The description is one tight, front-loaded clause followed by a brief pagination note and a cost parenthetical. Every phrase earns its place and there is no redundant restatement of the tool name or schema.

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

Completeness3/5

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

The description gives a solid high-level overview, and the rich annotations plus output schema cover safety and return structure. However, the tool has 33 optional parameters and a closely related sibling search_people_live; the description does not clarify the dataset-vs-live distinction or provide selection guidance, leaving an important gap for an agent choosing between siblings.

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 all 33 parameters. The description adds a useful high-level list of filter categories, but it does not add parameter-specific meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 opens with a specific verb and object — 'Search professional records' — and enumerates the main filter dimensions (name, title, company, skills, education, tenure, geography). However, it does not explicitly differentiate this tool from sibling search_people_live or search_alumni, so the agent must infer which variant this is.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention search_people_live, search_alumni, or any exclusion criteria, leaving the agent without decision support for choosing among the search-family siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.