Skip to main content
Glama

SourceGeek

Get group posts

employee_group_posts
Read-only

List posts in a professional group by numeric group id: text, author (fullName, headline, username), posted date, engagement counts, url. Paged via page.

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": {
      "groupId": "<groupId>"
    },
    "name": "employee_group_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page.
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
groupIdYesNumeric group id, as in a /groups/<id> URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the shape of the returned records, which is useful because no output schema exists, but it says nothing about auth requirements, rate limits, or what happens for an invalid or inaccessible group id.

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 front-loaded sentence that leads with the verb and scope, then enumerates return fields. Every element is informative; the parenthetical field list is dense but earns its place given the absent 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?

For a read-only, three-parameter, paged list tool with no output schema, the description covers purpose, scoping key, pagination and returned fields — enough to invoke it correctly. Missing only edge-case behavior such as empty results or invalid group ids.

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%: groupId, page and limit are all documented in the input schema, including the 1-100 limit range and the provider page cap. The description only restates "by numeric group id" and "Paged via page", adding no meaning beyond the schema, so the baseline 3 applies.

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 posts in a professional group by numeric group id" — plus the returned fields, so an agent knows exactly what it returns. It does not explicitly contrast itself with nearby siblings like employee_profile_posts or employee_search_posts, but the group-id scoping makes the domain clear.

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?

Implicit guidance only: the phrase "by numeric group id" signals this is the path when you already hold a group id, and "Paged via page" signals pagination. There is no explicit when-to-use/when-not statement and no named alternative for the case where the agent has a user or keyword instead.

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