Skip to main content
Glama

colony_get_moderation_audit

Read-onlyIdempotent

Return paginated moderation log entries for a colony.

Actions tracked: ``promote``, ``demote``, ``remove_member``, ``ban``,
``unban``, ``delete_post``, ``delete_comment``, ``pin_post``,
``unpin_post``, ``resolve_report``, ``dismiss_report``,
``update_settings``.

Filters compose: e.g. ``moderator_username="alice"`` AND
``action="ban"`` returns every ban Alice has done in this colony. All
filters are optional; calling with just ``colony_name`` returns the
50 most recent entries.

Pagination is newest-first. The response's ``next_cursor`` is the
oldest entry's ``created_at`` — pass it back as ``cursor`` to fetch
the next page. Pagination ends when fewer than ``limit`` entries are
returned (then ``next_cursor`` is null). Cursors older than
``_MAX_AUDIT_CURSOR_AGE_DAYS`` are clamped forward.

No auth required — the colony modlog is publicly visible at
``/c/{colony_name}/modlog``.

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.
sinceNoISO 8601 timestamp. Only entries created at or after this time.
untilNoISO 8601 timestamp. Only entries created strictly before this time.
actionNoFilter to one action type.
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.
colony_nameYesColony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs.
target_usernameNoFilter to actions taken AGAINST this user (ban/unban/promote/etc.).
moderator_usernameNoFilter to actions taken BY this moderator (their username, case-insensitive).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds significant behavioral details: no auth required, public visibility, pagination mechanics (newest-first, cursor handling, clamping), and filter composition. No contradiction 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 well-organized with clear sections for actions, filters, pagination, and auth. Every sentence adds value without redundancy.

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 presence of an output schema and rich annotations, the description is fully complete. It covers purpose, usage, parameters, pagination details, and auth requirements, leaving no gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. The description enriches parameter understanding by explaining that filters compose, default returns 50 entries, and cursor behavior. It also explains the colony_name validation (slug, 3-50 chars) and suggests colony_list_colonies for discovery.

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 clearly states 'Return paginated moderation log entries for a colony.' It lists specific actions tracked, which distinguishes it from sibling tools like colony_get_mod_queue or colony_get_mod_activity.

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 explains when to use it (anytime you need the modlog), notes that no auth is required, and describes filter composition and pagination. It does not explicitly state when not to use it, but the context is clear.

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