ZOOQ - LinkedIn Data for AI Agents

posts_info

Read-onlyIdempotent

Full content of one post (returned under data.post). For comments use /posts/comments. (Costs 10 Zooq credits.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entityId": "<entityId>"
    },
    "name": "posts_info"
  }
}

Input Schema

Name	Required	Description	Default
`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

Name	Required	Description	Default
`post`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark the operation as read-only and idempotent; the description adds value by disclosing the 10-credit cost and noting the data.post return path. There is no contradiction with the 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 compact and front-loaded: purpose first, then the routing rule, then the cost. Every clause earns its place with no filler or repetition.

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?

For a one-parameter, read-only tool with a rich schema and an output schema, this description covers the essential calling context: single-post scope, return path, comments alternative, and credit cost. Nothing critical 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?

The single parameter entityId is fully documented in the schema, including accepted formats and how to obtain it from companies_posts. Since schema coverage is 100%, the description need not add parameter detail; it adds none.

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 that the tool returns the full content of one post and specifies the response location (data.post), which is specific and actionable. It also distinguishes itself from the comments tool by explicitly routing comment requests to /posts/comments.

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

Usage Guidelines5/5

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

It provides a clear when-not/alternative rule: use /posts/comments for comments. It also scopes the call to a single post, so an agent knows this is not for listing or bulk retrieval.

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

All ZOOQ - LinkedIn Data for AI Agents 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.