Skip to main content
Glama

SourceGeek

Get post reactions

employee_post_reactions
Read-only

List the people who reacted to a public post by URL: fullName, headline, profile URL, reaction type. Optional reactionType filter; paged via page with total/totalPages.

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": {
      "postUrl": "<postUrl>"
    },
    "name": "employee_post_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
postUrlYesPost URL.
reactionTypeNoOptional filter such as LIKE, PRAISE, EMPATHY, INTEREST, APPRECIATION.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are limited to public posts (a real access constraint) and responses are paged with total/totalPages metadata. It does not mention auth or rate-limit behavior, but the added constraint and pagination detail are meaningful.

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?

One dense sentence front-loads the action, resource, and returned fields, then tacks on the filter and pagination modifiers. Every clause carries information and there is no boilerplate padding.

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?

With no output schema, the description usefully enumerates return fields and mentions pagination totals, so an agent knows the response shape. It is nearly complete for a simple read tool; only the partial-results caveat about the provider page (documented in the schema) is left out of the prose.

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 postUrl, page, limit, and reactionType are all documented in the schema, including the reaction enum examples and the 1-100 limit cap. The description restates the reactionType filter and page pagination without adding format or edge-case detail, leaving the baseline of 3 appropriate.

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 uses a specific verb and resource ('List the people who reacted to a public post by URL') and enumerates the returned fields (fullName, headline, profile URL, reaction type), so the agent knows exactly what the tool yields. It implicitly distinguishes itself from the comment and repost siblings via 'reacted', but never names an alternative explicitly.

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?

It states an optional reactionType filter and page-based pagination, which implies when to use those parameters, and it implicitly restricts use to public posts. There is no explicit when-to-use vs. when-not guidance relative to sibling tools such as employee_post_comments or employee_profile_reactions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources