Skip to main content
Glama

SourceGeek

Get a person's reactions

employee_profile_reactions
Read-only

List the public posts a person reacted to: reaction action, entity type and the post (text, url, author, engagement). Paged via start (0, 100, 200…) and paginationToken.

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": {
      "usernameOrUrl": "<usernameOrUrl>"
    },
    "name": "employee_profile_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
startNoProvider offset for the next page (echoed back as nextStart by the previous call). Omit for the first page.
usernameOrUrlYesA profile username such as 'janedoe' or a public profile URL ending in /in/janedoe.
paginationTokenNoOpaque token from the previous call's paginationToken; required together with start when fetching the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this as a safe, read-only, open-world call, so the bar is lower; the description still adds that only public posts are returned and what each record contains. That is meaningful context beyond the annotations, though it says nothing about auth requirements or result-size behavior beyond paging.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two sentences, front-loaded with the purpose and payload, followed by paging. Dense and free of filler, though the paging clause slightly duplicates what the schema already spells out.

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?

Absent an output schema, the description usefully enumerates the returned fields and explains how to advance pages, which is what an agent needs to call and continue correctly. It stops short of nothing critical for a single required-parameter read tool.

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 coverage is 100%, with limit, start, paginationToken and usernameOrUrl all described in the schema, so the baseline of 3 applies. The description restates the paging flow ('start (0, 100, 200…) and paginationToken') at the same level of detail the schema already provides rather than adding new semantics.

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 gives a specific verb and resource ('List the public posts a person reacted to') and enumerates the returned content ('reaction action, entity type and the post (text, url, author, engagement)'). The 'reacted to' scoping cleanly separates it from sibling readers such as employee_profile_posts or employee_profile_comments without needing to name them.

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?

Usage is implied rather than stated: an agent can infer it is for a person's reaction feed, and the pagination sentence describes the mechanics of continuing past page one. There is no explicit when-to-use vs. when-not block and no named alternative, so guidance remains implicit.

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