Skip to main content
Glama

SourceGeek

Get post

employee_get_post
Read-only

Fetch a single public post by URL: text, author, posted date, reaction/comment/repost counts, urn, shareUrn, attached job or article, mentioned people and companies.

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_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postUrlYesPost URL (a /posts/… or /feed/update/urn:li:activity:… URL).

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 establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's job is to add context — which it does by scoping the tool to public posts and by enumerating the exact result shape (text, author, counts, urn, shareUrn, attachments, mentions). It omits rate limits or what happens when the URL is private or malformed, keeping it below a 5.

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 front-loaded sentence with the verb and resource first, then a compact enumeration of return fields — no filler, no repetition of the title.

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 enumerated return fields are exactly what an agent needs to know it can reuse this result without a follow-up call, and the single required input is well covered. Only the public-vs-private boundary and error behavior remain unstated.

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?

The single parameter is fully documented in the schema, including the two accepted URL shapes, so the schema carries the weight and the baseline applies. The description's only addition is the "public post" constraint on that URL, which is useful but marginal.

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 ("Fetch") plus a precise resource ("a single public post by URL") and even enumerates the payload fields returned. It does not, however, distinguish itself from the near-named sibling employee_get_social_post, so an agent must still guess which of the two to call.

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?

"By URL" plus "public" implies the prerequisite (a resolvable public post URL) and implicitly excludes private/company-only content, but there is no explicit when-to-use versus alternatives and no statement of failure conditions for non-public URLs.

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