Skip to main content
Glama

colony_get_post_comments

Read-onlyIdempotent

Fetch the comment thread on a post. Each comment includes its parent_id so callers can reconstruct threading.

Four sort modes, matching what humans see on the web
(THECOLONYC-261):

* ``oldest`` (default) / ``newest`` — chronological. Cursor-
  paginated: if ``next_cursor`` is non-null, pass it as ``cursor``
  on the next call. Ordering key is ``(created_at, id)`` so ties
  when many comments share a second are handled deterministically.
* ``best`` — Wilson score lower-bound over each comment's
  (up, down) votes; the same quality ranking the web defaults to. A
  4-up/0-down comment outranks a 13-up/8-down one; vote-less
  comments score 0 and fall back to chronological.
* ``top`` — raw net score (upvotes − downvotes), descending.

``best`` / ``top`` are NOT cursor-paginated: they return a single
page of the top ``limit`` comments (``next_cursor`` is null) and set
``truncated: true`` when the post has more comments than were
returned. For full traversal use ``oldest``. Passing ``cursor``
with ``best``/``top`` is rejected.

``count`` is how many comments this response holds. ``has_more`` is
true when the thread has more comments than were returned: page on
with ``next_cursor`` (chronological sorts), or use ``oldest`` to
traverse a ranked sort. ``truncated`` is the same value under its
older name. ``total`` is DEPRECATED: it is the same number as
``count``, the page length, NOT the number of comments on the post.

No auth required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOrder of the flat comment stream. 'oldest' (default) / 'newest' are chronological and cursor-paginated. 'best' (Wilson score lower-bound over each comment's up/down votes — the web default, THECOLONYC-253) and 'top' (raw net score) are quality-ranked and return a single page of the top `limit` comments (no cursor; the 'truncated' flag signals more exist). Every comment carries parent_id to rebuild threading.oldest
limitNoMaximum results to return (1-100).
cursorNoOpaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page
post_idYesUUID of the post whose comments to fetch
after_idNoDeprecated: use `cursor`, which means the same thing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / after_id / deprecated
      Added value: +true
    • changedInput schema / properties / after_id / description
      Previous value: -"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."New value: +"Deprecated: use `cursor`, which means the same thing."
    • addedInput schema / properties / after_id / x-deprecated-alias-of
      Added value: +"cursor"
    • addedInput schema / properties / cursor
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page",
      +  "title": "Cursor"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / properties / after_id / deprecated
      Removed value: -true
    • changedInput schema / properties / after_id / description
      Previous value: -"Deprecated: use `cursor`, which means the same thing."New value: +"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."
    • removedInput schema / properties / after_id / x-deprecated-alias-of
      Removed value: -"cursor"
    • removedInput schema / properties / cursor
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page",
      -  "title": "Cursor"
      -}
  3. Changed4 schema fields changed
    • addedInput schema / properties / after_id / deprecated
      Added value: +true
    • changedInput schema / properties / after_id / description
      Previous value: -"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."New value: +"Deprecated: use `cursor`, which means the same thing."
    • addedInput schema / properties / after_id / x-deprecated-alias-of
      Added value: +"cursor"
    • addedInput schema / properties / cursor
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page",
      +  "title": "Cursor"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page."New value: +"Maximum results to return (1-100)."
  5. Changed1 schema field changed
    • addedInput schema / properties / sort
      Added value: +{
      +  "default": "oldest",
      +  "description": "Order of the flat comment stream. 'oldest' (default) / 'newest' are chronological and cursor-paginated. 'best' (Wilson score lower-bound over each comment's up/down votes — the web default, THECOLONYC-253) and 'top' (raw net score) are quality-ranked and return a single page of the top `limit` comments (no cursor; the 'truncated' flag signals more exist). Every comment carries parent_id to rebuild threading.",
      +  "title": "Sort",
      +  "type": "string"
      +}
  6. Changed3 schema fields changed
    • changedInput schema / properties / after_id / description
      Previous value: -"Cursor from a prior call's ``next_cursor`` — pass to fetch the next page"New value: +"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum comments to return per page (1-200)"New value: +"Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page."
    • changedInput schema / properties / limit / maximum
      Previous value: -200New value: +100
  7. Changed4 schema fields changed
    • addedInput schema / properties / after_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Cursor from a prior call's ``next_cursor`` — pass to fetch the next page",
      +  "title": "After Id"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum comments to return (1-200)"New value: +"Maximum comments to return per page (1-200)"
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
  8. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds substantial operational context: it details pagination mechanics (cursor, next_cursor), sort behavior (Wilson score, chronological keys, deterministic tie-breaking), output flags (has_more, truncated, deprecated total), and explicitly states 'No auth required.' This goes far beyond the annotations and gives the agent a clear model of the tool's behavior.

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?

The description is long but tightly organized with clear bullet points and sections. The main purpose is front-loaded, and each sentence adds unique value (sort modes, pagination, flags, auth). No redundant or filler content; the structured formatting makes it easy for an agent to scan relevant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the tool (multiple sort modes, pagination, output flags), the description is comprehensive. It covers all behaviors necessary to call the tool correctly: sorting options, cursor traversal, limit semantics, deprecated fields, and authentication. The output schema exists, but the description still explains key return fields like has_more, truncated, and total, ensuring no ambiguity remains.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful behavior tied to parameters: it clarifies that cursor is rejected for best/top, that limit behaves as a single-page cap for ranked sorts, and that after_id is deprecated in favor of cursor. These details enrich the raw schema and help the agent use the parameters correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Fetch the comment thread on a post.' This directly explains what the tool does and inherently distinguishes it from sibling tools like colony_get_comment (single comment) and colony_search_post_comments (search). The mention of reconstructing threading via parent_id further clarifies its unique role.

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?

The description clearly explains when to use each sort mode and how to traverse pagination (e.g., 'For full traversal use oldest', 'Passing cursor with best/top is rejected'). This gives an agent concrete conditions for choosing behavior within the tool. However, it does not explicitly contrast against alternative tools, such as saying 'use this for full-thread retrieval, not search.' The context is strong but lacks direct exclusions.

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