Skip to main content
Glama

SourceGeek

Get post by URL

employee_get_social_post
Read-only

Fetch a single public post by URL via the provider's alternate 'social post' route: text, author, posted date, engagement counts and urn. Use it when the standard post lookup fails.

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

Input Schema

NameRequiredDescriptionDefault
postUrlYesPost URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the description's job is to add nuance. It does: it discloses that only public posts are reachable, that this is a secondary route, and it lists the fields returned, which is valuable since no output schema exists. It says nothing about rate limits, auth, or error behavior on inaccessible posts.

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?

A single sentence that front-loads the action, then the payload, then the usage condition. No filler and no repetition of annotation-declared traits.

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?

For a one-parameter read tool with no output schema, the description supplies both the return shape and the fallback positioning, which is close to sufficient. The main gap is that 'when the standard lookup fails' is not operationalized, leaving the agent to guess at failure modes.

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 a single required URI-formatted postUrl, so the schema does the heavy lifting. The description contributes only the constraint that the URL must point to a public post, which is a modest addition over the schema's 'Post URL.' field text.

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 concrete verb and resource (fetch a single public post by URL) and enumerates the return payload: text, author, posted date, engagement counts, urn. It also distinguishes itself as the 'alternate social post route', implicitly the fallback for employee_get_post, though it never names that sibling outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it when the standard post lookup fails' gives a clear selection condition and identifies the preferred tool by role. No explicit exclusions or prerequisites (e.g. what counts as 'fails') are given, so it stops short of a full when-to/when-not pair.

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