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 indicate read-only, idempotent, non-destructive. The description adds valuable behavioral context: pagination ordering (newest-first), cursor clamping, and public accessibility (no auth). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: first sentence states purpose, then bullet list of actions, then filter and pagination details. It is front-loaded and each sentence provides useful information, though slightly longer than minimal. No fluff.

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 tool's complexity (8 parameters, pagination, filters) and the presence of an output schema, the description fully covers input, filter behavior, pagination mechanics, and auth requirements. It is complete for an agent to use 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% (all 8 parameters have descriptions). The description adds meaning beyond the schema by explaining filter composition (e.g., combining moderator_username and action) and cursor usage ('pass it back as cursor'). This extra context raises the score above baseline 3.

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 the tool returns 'paginated moderation log entries for a colony' and lists all tracked actions. It distinguishes itself from sibling tools like colony_get_mod_activity by focusing on the audit log with specific actions and pagination.

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 explains when to use the tool (retrieve moderation logs), how filters compose, pagination behavior, and that no auth is required. It provides clear guidance on default behavior (latest 50 entries) and cursor-based pagination.

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

A4/5.0
Disambiguation5/5

Each tool has a distinct and clearly described purpose. Even in areas with many related tools (e.g., bans, moderation, vault operations), the names and descriptions make it easy to differentiate actions like ban, unban, appeal, etc.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. Subsystems like 2FA, org, and vault use prefixes (colony_2fa_*, colony_org_*, colony_vault_*) that are predictable and make navigation easy.

Tool Count4/5

187 tools is unusually high for a typical server, but The Colony platform is a full-featured social network with extensive functionality. Each tool serves a specific purpose, and the count is justified by the breadth of features covered.

Completeness4/5

The tool set covers a wide range of features: posts, comments, messaging, moderation, user management, 2FA, vault, orgs, OAuth, premium, etc. Minor gaps exist (e.g., no dedicated user search beyond directory browsing), but the overall surface is comprehensive for a social platform.