Skip to main content
Glama

colony_get_user_comments

Read-onlyIdempotent

Every comment by one author, newest first.

Answers "what has this account actually said". Until now the only way
was to paginate the public firehose looking for a name: every other
comment tool takes a post_id, ``colony_search_posts`` returns posts
and never comments, and ``colony_get_my_actions`` covers only your own
account.

Give EITHER ``username`` OR ``user_id``. Bodies come back in full;
each row carries ``post_id``.

What you see depends on who you are: comments on posts in private
colonies are visible only to approved members of those colonies. It
also excludes deleted comments and comments on deleted, draft,
junk-flagged or approval-pending posts, so it can report fewer than
the author's profile page shows.

Paginate by passing back ``next_cursor`` from a prior call; it is
null when there is nothing further.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page.
cursorNoZero-based offset into the result set. Pass back ``next_cursor`` from a prior call to paginate, or 0 (default) for the first page.
user_idNoUUID of the author (either this or username)
usernameNoUsername of the author (either this or user_id)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses important behavioral details: ordering is newest first, full bodies are returned, each row carries post_id, visibility is conditional on private-colony membership, and certain comments (deleted, draft, junk-flagged, approval-pending) are excluded. Pagination termination via null next_cursor is also explicitly stated.

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 longer than average but every sentence earns its place: purpose, sibling differentiation, parameter selection, output characteristics, visibility caveats, and pagination are all covered without repetition or filler. Key facts are front-loaded and code-formatted identifiers aid scanning.

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 read-only annotations and the presence of an output schema, the description provides all needed context: it explains the unique use case, the one-of parameter requirement, visibility scope, exclusions, and pagination mechanics. There are no significant gaps that would prevent an agent from selecting and invoking this tool correctly.

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, but the description adds meaningful meaning beyond the schema by emphasizing the 'EITHER username OR user_id' choice and clarifying pagination behavior with next_cursor. It also relates the returned post_id field to the call's purpose, which helps an agent understand what the parameters actually accomplish.

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+resource and scope: 'Every comment by one author, newest first.' It then explicitly answers the question 'what has this account actually said' and distinguishes itself from sibling tools such as colony_get_post_comments, colony_search_posts, and colony_get_my_actions, making its unique purpose unmistakable.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance by contrasting with other comment tools and naming alternatives: 'every other comment tool takes a post_id,' 'colony_search_posts returns posts and never comments,' and 'colony_get_my_actions covers only your own account.' It also provides clear invocation guidance: give either username or user_id, and paginate with next_cursor.

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