Zooq

posts_comments

Read-onlyIdempotent

Threaded comments/replies on a post. (Costs 10 Zooq credits.)

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	Results per page (default 10).
`start`	No	Pagination offset.
`sortBy`	No	Ordering. Accepted values: relevance (default), date_posted (newest first).
`entityId`	Yes	Activity id — bare numeric or urn:li:activity: form, both accepted. Get it from companies_posts — read data.activities[].entityId (person feeds are currently unavailable).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`replies`	No	Array in the example

Schema Changelog

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

Changed1 schema field changedAug 27, 2026

changedInput schema / properties / entityId / description

Previous value: -"Activity id — bare numeric or urn:li:activity: form, both accepted. Get it from /api/v1/companies/posts — read data.activities[].entityId (person feeds are currently unavailable)."New value: +"Activity id — bare numeric or urn:li:activity: form, both accepted. Get it from companies_posts — read data.activities[].entityId (person feeds are currently unavailable)."

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": {
+    "replies": {
+      "description": "Array in the example",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "author": {
+            "additionalProperties": true,
+            "properties": {
+              "headline": {
+                "description": "Example value was a string"
+              },
+              "name": {
+                "description": "Example value was a string"
+              }
+            }
+          },
+          "comment": {
+            "description": "Example value was a string"
+          },
+          "createdAt": {
+            "description": "Example value was a string"
+          },
+          "edited": {
+            "description": "Example value was a boolean"
+          },
+          "engagements": {
+            "additionalProperties": true,
+            "properties": {
+              "reactions": {
+                "description": "Example value was a number"
+              }
+            }
+          },
+          "permalink": {
+            "description": "Example value was a string"
+          }
+        }
+      }
+    }
+  },
+  "type": "object"
+}

First observedAug 24, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers safety. The description adds meaningful behavioral context beyond annotations by disclosing the 10 Zooq credit cost and the threaded nature of the results, both of which an agent would not know from the schema alone.

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 two short sentences with zero filler. The core purpose is front-loaded, and the credit cost is appended as a brief, useful caveat. Every word earns its place.

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

Completeness4/5

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

Given the output schema exists, annotations cover safety, and the input schema documents all parameters, the description is nearly complete for invocation. The only notable gap is routing guidance relative to sibling tools, but that is not critical for a straightforward read-only list operation.

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, sortBy, and entityId, including accepted entityId formats and where to source it. The description adds no parameter-level detail, but none is needed because the schema carries that burden completely.

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 as threaded comments/replies on a post, and the annotation title 'List post comments' reinforces the action. It does not explicitly state a verb in the description itself, and it does not explicitly contrast with siblings like comments_all or posts_likes, but the resource and scope are unambiguous.

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?

No guidance is given for when to use this tool versus alternatives such as comments_all, posts_likes, or posts_all. The schema does mention that entityId comes from companies_posts, which is indirect usage context, but the description itself provides no when-to-use or when-not-to-use direction.

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?