Skip to main content
Glama

SourceGeek

Get post reposts

employee_post_reposts
Read-only

List the people who reposted a public post by post urn (activity id, urn:li:activity:… or post URL): person summary and repost date; paged via page 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": {
      "postUrn": "<postUrn>"
    },
    "name": "employee_post_reposts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
postUrnYesPost urn / activity id (or a post URL containing it).
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.7/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 safety is covered. The description adds value beyond them by disclosing the returned content (person summary plus repost date) and the paging mechanism, which are not in the annotations; it omits any mention of auth or rate limits.

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?

A single dense sentence with the resource front-loaded, followed by return fields and paging. Punctuation-separated clauses keep it compact; it is slightly crammed but no sentence is wasted.

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 carries the burden of describing results and does so at a summary level (person summary, repost date). Paging is explained and the urn input format is covered, which is adequate for a simple read-only listing 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 description coverage is 100%, so the schema already documents page, limit, postUrn and paginationToken, including the 1-100 limit cap. The description only restates the urn format and paging parameters, adding no meaning beyond the schema and not mentioning limit at all.

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 the people who reposted a public post by post urn', and enumerates the returned fields (person summary, repost date). An agent can distinguish this from reaction/comment listing tools by the resource itself, though no sibling is named 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?

Usage is implied by the resource description and the 'public post' scoping, so an agent can infer when to reach for it. There is no explicit when-not guidance or named alternative (e.g. reactions vs reposts, or profile-post variants), leaving routing to inference.

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