Skip to main content
Glama
Sign In

LinkedIn Pages MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

LinkedIn Pages Data Query

query_data
Read-only

Query LinkedIn Pages data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

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": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a non-mutating external read, and an output schema covers return shape. The description adds the workflow ordering constraint, which is real value, but says nothing about rate limits, pagination, or what a malformed body does. 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The numbered prerequisite list is front-loaded and scannable, but the step-2 requirement is stated twice (once in the numbered list, once as an "IMPORTANT" restatement), which is wasted space in a short description.

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

Completeness3/5

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

Output schema and annotations cover return values and the read-only/external profile, so those gaps are handled. What remains thin is the opaque body parameter: the description tells the agent where to source its structure but not what a valid body looks like, and the workflow means three round trips before any query succeeds.

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

Parameters2/5

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

The single parameter is an untyped object with additionalProperties: true and 0% schema description coverage, and the description offers no field-level semantics at all. It partially compensates by directing the agent to query_contexts/actions_details for the body structure, but "Follow the schema exactly" points at a schema that defines nothing, leaving the parameter effectively undocumented.

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?

"Query LinkedIn Pages data" names a specific verb and resource and pins its position in a workflow ("Step 3 (FINAL)"), so an agent knows this is the execution step. It does not, however, distinguish itself from the sibling execute_action, nor does it say what kind of data is returned.

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 is unusually prescriptive about preconditions: it names the exact query_contexts calls (request='accounts', then request='actions_details') that must precede it and insists step 2 is never skipped. It never states when NOT to use this tool or how it relates to execute_action, so it stops short of a 5.

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

All LinkedIn Pages MCP by InsightfulPipe toolsInspect
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