Zooq

posts_all

Read-onlyIdempotent

A person's recent posts / activity stream. Cursor- or offset-paginated. Keyed by the person entityId: pass handle and Zooq resolves it for you at no extra credit cost, or pass entityId from profile_entity_id to skip the lookup. (Costs 10 Zooq credits.)

Input Schema

TableJSON Schema

Name	Required	Description
`start`	No	Pagination offset (alternative to cursor).
`cursor`	No	Opaque pagination cursor (preferred) from the previous response's nextCursor.
`handle`	No	Public profile handle — the part after linkedin.com/in/ — or the full profile URL. Resolved to `entityId` automatically at no extra credit cost. Any person identifier is accepted here and sorted by format (handle, URL, ACoAA… entityId, prsn_ id). Provide `entityId` OR `handle`; `handle` is the simplest.
`entityId`	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 `entityId` OR `handle`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`activities`	No	Array in the example
`nextCursor`	No	Example value was a string

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / entityId / description

Previous value: -"Person entityId from /api/v1/profile/entity-id or /api/v1/profile/enrich. NOT the prsn_ id from /profile/username-to-urn — that is the dataset namespace and the live endpoints reject it. Provide `entityId` OR `handle`."New value: +"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 `entityId` OR `handle`."

changedInput schema / properties / handle / description

Previous value: -"Public profile handle — the part after linkedin.com/in/. Resolved to `entityId` automatically at no extra credit cost. Provide `entityId` OR `handle`."New value: +"Public profile handle — the part after linkedin.com/in/ — or the full profile URL. Resolved to `entityId` automatically at no extra credit cost. Any person identifier is accepted here and sorted by format (handle, URL, ACoAA… entityId, prsn_ id). Provide `entityId` OR `handle`; `handle` is the simplest."

Changed1 schema field changedAug 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Structural schema derived from a live example — field names and nesting only, no type constraints: fields may be absent, null, or a different primitive than the example, and new fields may appear. The text content block carries the same JSON.",
+  "properties": {
+    "activities": {
+      "description": "Array in the example",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "author": {
+            "additionalProperties": true,
+            "properties": {
+              "entityId": {
+                "description": "Example value was a string"
+              },
+              "fullName": {
+                "description": "Example value was a string"
+              },
+              "handle": {
+                "description": "Example value was a string"
+              }
+            }
+          },
+          "commentsCount": {
+            "description": "Example value was a number"
+          },
+          "id": {
+            "description": "Example value was a string"
+          },
+          "media": {
+            "description": "Array in the example",
+            "items": {}
+          },
+          "postedAt": {
+            "description": "Example value was a string"
+          },
+          "reactionsCount": {
+            "description": "Example value was a number"
+          },
+          "repostsCount": {
+            "description": "Example value was a number"
+          },
+          "text": {
+            "description": "Example value was a string"
+          },
+          "url": {
+            "description": "Example value was a string"
+          }
+        }
+      }
+    },
+    "nextCursor": {
+      "description": "Example value was a string"
+    }
+  },
+  "type": "object"
+}

First observedAug 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds meaningful behavior beyond that: cursor/offset pagination, automatic handle resolution, the ability to skip lookup with entityId, and a concrete 10-Zooq-credit cost. No contradiction with 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?

Two dense sentences front-load the core purpose and pagination, then cover identity resolution and cost with no filler. Every clause adds actionable information.

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?

With an output schema present and annotations covering the safety profile, the description fully covers the key operational details: pagination, identity resolution, credit cost, and the handle/entityId distinction. Nothing essential for calling the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds useful semantic context around handle versus entityId: handle is resolved automatically at no extra credit cost, while entityId skips the lookup. This clarifies the trade-off between the two identity parameters beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: 'a person's recent posts / activity stream.' This clearly distinguishes the tool from sibling tools like companies_posts, posts_info, posts_comments, and posts_likes by emphasizing the person-level feed context.

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 provides clear context for use: retrieving a person's recent posts. It gives practical guidance on choosing between handle and entityId, but it does not explicitly state when not to use this tool or name alternative tools for single-post, comment, or like lookups.

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?