Skip to main content
Glama
Sign In

mcp

by com.makehybrid
OverviewDiscussionsAdmin

MakeHybrid API: List all Post's Reactions

complete_posts_reactions
Read-onlyIdempotent

List all Post's Reactions -- MakeHybrid API plan, GET /linkedin/v2/{account_id}/posts/{post_id}/reactions, group posts.

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": {
      "account_id": "<account_id>",
      "post_id": "<post_id>"
    },
    "name": "complete_posts_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional query-string parameters, e.g. {"limit":"20","cursor":"..."}. Values are coerced to strings.
post_idYesValue for the {post_id} segment of /linkedin/v2/{account_id}/posts/{post_id}/reactions. Required; pass it raw (it is URL-escaped for you).
account_idYesValue for the {account_id} segment of /linkedin/v2/{account_id}/posts/{post_id}/reactions. Required; pass it raw (it is URL-escaped for you).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered. The description adds the concrete API surface (v2 endpoint, segment-based path parameters), but says nothing about pagination/cursor semantics despite the schema exposing a cursor, nor about rate limits or result shape.

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?

It is a single short sentence with the verb front-loaded, which is good. However the dash-separated appendices ("MakeHybrid API plan", "group posts") read as metadata noise rather than actionable information, so not every fragment earns its place.

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?

For a simple read-only list tool with a fully documented schema, the essentials are present. Gaps remain on pagination behavior (cursor/limit) and what a reaction record contains, which matters since there is no output schema to fall back on.

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%, with each parameter documented inline including URL-escaping behavior, so the baseline of 3 applies. The description repeats only that account_id and post_id are path segments and adds no further meaning about the nested query object.

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?

States a specific verb and resource ("List all Post's Reactions") plus the exact upstream endpoint GET /linkedin/v2/{account_id}/posts/{post_id}/reactions, so an agent can pin down the operation. It does not differentiate from the near-identical sibling complete_posts_comments, and the trailing fragment "group posts" muddies rather than clarifies scope.

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?

There is no statement of when to use this versus alternatives such as complete_posts_get or complete_posts_comments, and no prerequisites or exclusions are given. Usage is only inferable from the endpoint path, and the ambiguous "group posts" tag adds no usable routing signal.

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

All mcp 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