Zooq

jobs_posted_by_profile

Read-onlyIdempotent

Job postings authored by a person (a recruiter's, hiring manager's or founder's roles). Includes closed postings (jobState). Only people who have posted jobs return results: for anyone else the upstream answers 422 "the data cannot be displayed or it doesn't exist" - that is a not-found, not a bad id. Find posters via jobs_hiring_team on a live posting. (Costs 10 Zooq credits.)

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	Results per page, 1-25 (default 10).
`start`	No	Pagination offset.
`handle`	No	Public profile handle — the part after linkedin.com/in/ — or the full profile URL. Resolved to `personEntityId` automatically at no extra credit cost. Any person identifier is accepted here and sorted by format (handle, URL, ACoAA… entityId, prsn_ id). Provide `personEntityId` OR `handle`; `handle` is the simplest.
`personEntityId`	No	Live person entityId (ACoAA…) from profile_entity_id / profile_enrich; the urn:li:fsd_profile: form is accepted. A prsn_ id (dataset namespace, from profile_full) or a handle placed here is recognized and translated automatically. Provide `personEntityId` OR `handle`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobs`	No	Array in the example
`total`	No	Example value was a number

TDQS

A4.3/5.0

Behavior5/5

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

The description adds significant behavioral context beyond the readOnly/openWorld/idempotent annotations: it reveals that closed postings are included, that non-poster profiles yield 422 interpreted as not-found, and that the call costs 10 credits. This materially helps an agent set expectations and handle errors correctly.

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 compact and every sentence adds value: scope, closed-post inclusion, not-found semantics, poster discovery via sibling tool, and cost. It is front-loaded with the primary purpose and uses parenthetical schema references economically.

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

Completeness5/5

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

The tool has an output schema, so return values need no narration. The description covers the core scope, an important error behavior, how to source input values, and cost. For a read-only listing tool with fully documented parameters, nothing essential is missing.

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 fully documents count, start, handle, and personEntityId. The description adds useful context about finding posters and the 422 behavior, but it does not add new meaning to the parameters themselves. A baseline of 3 is appropriate given the complete schema coverage.

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 identifies the resource: job postings authored by a specific person, including closed postings. It implicitly distinguishes itself from jobs_hiring_team by instructing users to find posters there first, and the resource differs from other sibling job tools. However, the description lacks an explicit verb phrase like 'List...' and does not contrast with search_jobs or companies_jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete guidance: use this tool after finding a poster via jobs_hiring_team, and interpret 422 as a not-found rather than an error. It also clarifies that only people who have actually posted jobs return results. It does not explicitly state when not to use the tool or name alternative tools for general job search.

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

All Zooq tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Many tools have strongly overlapping purposes: companies_name_lookup is explicitly equivalent to search_companies, companies_enrich/companies_info/companies_universal_name_to_id all return company-profile data, and profile_full overlaps with profile_employment_history and profile_enrich. The descriptions are detailed, but an agent would still frequently have to choose between near-duplicate endpoints.

Naming Consistency4/5

Tool names mostly follow a predictable resource-prefixed snake_case pattern, such as companies_*, jobs_*, posts_*, profile_*, and search_*, which makes the set readable and groupable. Minor inconsistencies like jobs_details_v2, g_title_skills_lookup, and mixed noun suffixes (info/details/full/lookup) keep it from a perfect score.

Tool Count2/5

44 tools is well beyond the heavy 25+ band, and several tools appear to be different lookup modes or near-duplicates of the same underlying capability. The broad LinkedIn-style data domain explains much of the size, but the set still feels bloated rather than well-scoped.

Completeness4/5

The API covers the core read-only professional-data workflows well: people, companies, jobs, posts, comments, likes, email discovery/verification, schools, skills, and targeted searches. Minor gaps exist, such as some job filters being unusable and no direct exposure of certain profile alias endpoints, but agents can generally complete end-to-end workflows.

Resources

Need Help?