Zooq

comments_all

Read-onlyIdempotent

Comments authored by a person across posts. Cursor-paginated. (Costs 10 Zooq credits.)

Input Schema

TableJSON Schema

Name	Required	Description
`start`	No	Pagination offset (alternative to cursor).
`cursor`	No	Opaque pagination cursor 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
`comments`	No	Array in the example
`nextCursor`	No	Example value was a string

Schema Changelog

Changes observed during successful MCP inspections.

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": {
+    "comments": {
+      "description": "Array in the example",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "activity": {
+            "additionalProperties": true,
+            "properties": {
+              "id": {
+                "description": "Example value was a string"
+              },
+              "url": {
+                "description": "Example value was a string"
+              }
+            }
+          },
+          "id": {
+            "description": "Example value was a string"
+          },
+          "postedAt": {
+            "description": "Example value was a string"
+          },
+          "text": {
+            "description": "Example value was a string"
+          }
+        }
+      }
+    },
+    "nextCursor": {
+      "description": "Example value was a string"
+    }
+  },
+  "type": "object"
+}

First observedAug 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior. The description adds valuable behavioral context beyond annotations by noting cursor-based pagination and the 10 Zooq credit cost, which are not captured in the structured metadata. This is useful supplementary transparency for an agent deciding whether to call the tool.

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 three short sentences with no wasted words. The core purpose is front-loaded, followed by the key behavioral note on pagination and the credit cost. Every phrase earns its place.

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?

Given the rich input schema, output schema, and safety annotations, the description adds the only missing operational details: pagination style and credit cost. An agent has enough to select and invoke this tool correctly without further context.

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 parameters are fully documented in the input schema itself. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline score applies. No credit cost or behavior info is needed for the parameters since the schema covers them.

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 identifies the resource as comments authored by a person and scopes it across posts, which distinguishes it from a tool like posts_comments that would target comments on a single post. It lacks an explicit verb, though the title 'List a person's comments' supplies the action. Overall the purpose is clear and largely distinguishable from siblings.

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

Usage Guidelines3/5

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

The phrase 'authored by a person across posts' implies this tool is for retrieving a person's comments across multiple posts, but it does not explicitly state when to prefer it over alternatives such as posts_comments. No exclusions or when-not-to-use guidance is provided. Usage context is implied rather than explicit.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?