Skip to main content
Glama

SourceGeek

Get a person's posts

employee_profile_posts
Read-only

Fetch a person's public posts (text, posted date, reaction/comment/repost counts, urn, shareUrn, url, attached job or article), newest first. Optional postedAfter date filter; paged via start (0, 50, 100…) 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_posts"
  }
}

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.
postedAfterNoOnly posts newer than this date (ISO, e.g. '2026-01-01').
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

B3.4/5.0
Behavior3/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 ordering ('newest first') and the shape of returned items, but says nothing about what happens with private/nonexistent profiles or how deep pagination can go.

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 tight sentences, purpose and return contents front-loaded, with the filter and paging clauses trailing. The parenthetical field list is long but justified because there is no output schema.

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?

Given no output schema, spelling out the returned fields and ordering is the right compensation, and paging plus a date filter are both covered. The remaining gap is tool-selection context against the many sibling post/profile tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; however the description adds the example offset sequence 'start (0, 50, 100…)' which clarifies page granularity beyond the schema's generic 'provider offset' wording. No other parameter detail is added.

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 ('Fetch a person's public posts') and enumerates the returned fields (text, date, counts, urn, shareUrn, url, attachments) plus ordering ('newest first'). It does not name or distinguish itself from siblings like employee_search_posts or employee_profile_full_with_posts, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

The only guidance is mechanical: an optional postedAfter filter and paging via start/paginationToken. There is no statement of when to choose this over employee_search_posts, employee_group_posts, or employee_profile_recent_activity_time, and no prerequisites such as public-profile requirements.

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