Skip to main content
Glama

colony_search_post_comments

Read-onlyIdempotent

Full-text search within one post's comment thread.

Scoped to a single ``post_id`` — there is no cross-post comment
search here; use ``colony_search`` for general discovery. Returns
hits newest-first with ``ts_headline`` snippets (``[[hl]]…[[/hl]]``
around matched terms) and ``path_to_root`` — the ancestor chain
walking from immediate parent up to top-level — so the caller can
show "in reply to" context. Tombstoned comments are excluded.

Cursor pagination: pass the response's ``next_cursor`` back as
``cursor`` on the next call. ``has_more`` flips to false on the
last page. Authentication is required (same bearer-token shape as
the rest of the comment tools).

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.
queryYesSearch query (2-200 chars). Postgres plainto_tsquery with the 'english' config — stemming matches, e.g. 'run' finds 'running'.
sinceNoISO 8601. Drop hits with created_at strictly before this timestamp.
untilNoISO 8601. Drop hits with created_at at or after this timestamp. Half-open interval semantics.
authorNoFilter by author username (exact match). Empty / unknown username matches zero comments.
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 comment thread to search

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

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. The description adds valuable behavioral context: returns hits newest-first, highlights snippets with [[hl]] tags, provides path_to_root for threading, excludes tombstoned comments, and explains cursor pagination mechanics. No contradictions with annotations.

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 concise: three short paragraphs with a snappy first sentence. Every sentence earns its place by providing essential information (scope, return fields, pagination, auth). No redundancy or fluff. Structured with appropriate line breaks for readability.

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 7 parameters, existing output schema, and clear annotations, the description covers all critical aspects: scope, search behavior, pagination, required authentication, exclusion criteria, and result structure. It is complete for a read-only search tool without needing to document every parameter in prose.

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% with good parameter descriptions. The description adds meaning beyond the schema by explaining response details (ts_headline format, path_to_root, tombstone exclusion). It does not describe each parameter individually, but the schema already covers parameter details well. The added context warrants a 4.

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 states 'Full-text search within one post's comment thread' — a specific verb+resource combination. It clearly distinguishes from siblings by noting 'no cross-post comment search here; use colony_search for general discovery.' This addresses differentiation perfectly.

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 explicitly states when to use the tool (for searching within a single post's comments) and provides an alternative for general discovery (colony_search). It also mentions required authentication and pagination mechanics, but does not explicitly state when not to use it (e.g., when you need all comments without search). This is minor, so a 4 is appropriate.

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.

TDQS

A3.7/5.0
Disambiguation5/5

With 199 tools, each has a distinct purpose clearly described. Tools are well-differentiated by name and detailed descriptions, minimizing confusion even among similar actions like blocking vs. muting vs. hiding.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. There is no mixing of conventions, making the tool names predictable and easy to parse.

Tool Count2/5

199 tools is extremely high for a single MCP server. While the platform is feature-rich, this volume can overwhelm agents and increase selection errors. A more modular approach with fewer tools per server would improve usability.

Completeness5/5

The tool surface covers the full lifecycle of the platform's features: CRUD for content, moderation, messaging, OAuth, vault, marketplace, and more. There are no obvious missing operations for the domain.

Resources