Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Comments

post_comments
Read-onlyIdempotent

Retrieves comment threads for a published post, newest first, so you can review each conversation's commenter, status, classification, and last message.

Instructions

The comment threads on a published post, newest first. Each thread is a conversation (commenter as contact, status, classification, last message); read one with conversation_thread. Members see the threads they may see in the channel.

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": {
      "organizationId": "<organizationId>",
      "postId": "<postId>"
    },
    "name": "post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
limitNoMaximum items to return (default 10, max 50).
postIdYesThe post id (see post_list).
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read, so the description's job is to add context – and it does: newest-first ordering, the composition of each thread (commenter as contact, status, classification, last message), and the permission scoping that members only see threads visible in the channel. It says nothing about pagination behavior, but page/limit are schema-documented.

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: scope and ordering first, thread composition second, sibling routing woven in without a separate paragraph. Every clause carries information; nothing is repeated from the 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?

With no output schema, the description compensates by sketching the shape of each thread (contact, status, classification, last message) and the sort order. For a four-parameter, fully-annotated read tool this is nearly complete; only pagination/empty-result behavior is left implicit.

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 postId, organizationId, page, and limit all described inline, so the schema carries the parameter burden. The phrase 'on a published post' reinforces postId, but the description adds no format, default, or boundary detail beyond the schema.

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 names the resource precisely (comment threads on a published post) and states the ordering (newest first), which is enough to distinguish it from conversation_thread. It lacks an explicit verb such as 'list', but the noun phrase makes the read operation unambiguous.

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?

It explicitly routes the agent: 'read one with conversation_thread', establishing the list-then-fetch workflow. It gives no when-not-to-use conditions (e.g. filtering by status or date), but the boundary with the sibling is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools