Skip to main content
Glama

SourceGeek

Get a person's comments

employee_profile_comments
Read-only

List a person's recent public comment activity: their comment text, when they commented, and the post it was on (text, url, author, engagement).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
usernameOrUrlYesA profile username such as 'janedoe' or a public profile URL ending in /in/janedoe.

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 useful constraints beyond that — the activity is "public" and "recent" — but says nothing about ordering, result completeness, or truncation behavior; the pagination caveat lives only in the limit parameter's schema text.

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 with the resource stated first and return fields in a compact parenthetical; every phrase carries information. Slightly dense, but nothing is wasted and nothing important is buried.

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 simple two-parameter, read-only tool with no output schema, the description usefully sketches the return payload (comment text, timestamp, post metadata with engagement), which is exactly what the missing output schema would otherwise require. Only ordering and truncation semantics remain unstated, and truncation is covered in the schema.

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%, with both limit (1-100, default 10, no cross-page fetching) and usernameOrUrl (username or /in/ profile URL) fully documented in the schema. The description adds no parameter-level meaning of its own, 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?

The description pairs a specific verb ("List") with a specific resource ("a person's recent public comment activity") and enumerates the returned fields (comment text, timestamp, post text/url/author/engagement). This distinguishes it in practice from post-centric siblings like employee_post_comments, though it never names a sibling 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 only implied: an agent can infer it is for retrieving a given person's comments, and the required usernameOrUrl plus the limit parameter make the call shape obvious. There is no explicit when-to-use/when-not-to-use statement or pointer to employee_profile_posts or employee_post_comments as alternatives.

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