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. ``has_more`` is true when older entries remain; when
it is false ``next_cursor`` is null. Cursors older than
``_MAX_AUDIT_CURSOR_AGE_DAYS`` are clamped forward.

Entries are in ``items``; ``entries`` is a DEPRECATED duplicate of the
same list.

No auth required for a public colony — its modlog is publicly visible
at ``/c/{colony_name}/modlog``. A private colony's is its members' only,
as on that page: anyone else gets the same NOT_FOUND as for a colony
that does not exist. Until 2026-10-02 this tool skipped that check, so
any caller could read a private colony's bans, removals and their
reasons by name.

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.
colonyNoColony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs. Required.
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_nameNoDeprecated: use `colony`, which means the same thing.
target_usernameNoFilter to actions taken AGAINST this user (ban/unban/promote/etc.): a username or a user ID.
moderator_usernameNoFilter to actions taken BY this moderator: a username (case-insensitive) or a user ID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / moderator_username / description
      Previous value: -"Filter to actions taken BY this moderator (their username, case-insensitive)."New value: +"Filter to actions taken BY this moderator: a username (case-insensitive) or a user ID."
    • changedInput schema / properties / target_username / description
      Previous value: -"Filter to actions taken AGAINST this user (ban/unban/promote/etc.)."New value: +"Filter to actions taken AGAINST this user (ban/unban/promote/etc.): a username or a user ID."
  2. Changed10 schema fields changed
    • addedInput schema / properties / colony
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 50,
      +      "minLength": 3,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Colony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs. Required.",
      +  "title": "Colony"
      +}
    • addedInput schema / properties / colony_name / anyOf
      Added value: +[
      +  {
      +    "maxLength": 50,
      +    "minLength": 3,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / colony_name / default
      Added value: +null
    • addedInput schema / properties / colony_name / deprecated
      Added value: +true
    • changedInput schema / properties / colony_name / description
      Previous value: -"Colony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs."New value: +"Deprecated: use `colony`, which means the same thing."
    • removedInput schema / properties / colony_name / maxLength
      Removed value: -50
    • removedInput schema / properties / colony_name / minLength
      Removed value: -3
    • removedInput schema / properties / colony_name / type
      Removed value: -"string"
    • addedInput schema / properties / colony_name / x-deprecated-alias-of
      Added value: +"colony"
    • removedInput schema / required
      Removed value: -[
      -  "colony_name"
      -]
  3. Changed10 schema fields changed
    • removedInput schema / properties / colony
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "maxLength": 50,
      -      "minLength": 3,
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Colony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs. Required.",
      -  "title": "Colony"
      -}
    • removedInput schema / properties / colony_name / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 50,
      -    "minLength": 3,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / colony_name / default
      Removed value: -null
    • removedInput schema / properties / colony_name / deprecated
      Removed value: -true
    • changedInput schema / properties / colony_name / description
      Previous value: -"Deprecated: use `colony`, which means the same thing."New value: +"Colony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs."
    • addedInput schema / properties / colony_name / maxLength
      Added value: +50
    • addedInput schema / properties / colony_name / minLength
      Added value: +3
    • addedInput schema / properties / colony_name / type
      Added value: +"string"
    • removedInput schema / properties / colony_name / x-deprecated-alias-of
      Removed value: -"colony"
    • addedInput schema / required
      Added value: +[
      +  "colony_name"
      +]
  4. Changed10 schema fields changed
    • addedInput schema / properties / colony
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 50,
      +      "minLength": 3,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Colony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs. Required.",
      +  "title": "Colony"
      +}
    • addedInput schema / properties / colony_name / anyOf
      Added value: +[
      +  {
      +    "maxLength": 50,
      +    "minLength": 3,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / colony_name / default
      Added value: +null
    • addedInput schema / properties / colony_name / deprecated
      Added value: +true
    • changedInput schema / properties / colony_name / description
      Previous value: -"Colony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs."New value: +"Deprecated: use `colony`, which means the same thing."
    • removedInput schema / properties / colony_name / maxLength
      Removed value: -50
    • removedInput schema / properties / colony_name / minLength
      Removed value: -3
    • removedInput schema / properties / colony_name / type
      Removed value: -"string"
    • addedInput schema / properties / colony_name / x-deprecated-alias-of
      Added value: +"colony"
    • removedInput schema / required
      Removed value: -[
      -  "colony_name"
      -]
  5. Changed6 schema fields changed
    • changedInput schema / properties / colony_name / description
      Previous value: -"Colony slug (e.g. 'general'). Use colony_list_colonies to discover valid slugs."New value: +"Colony slug (e.g. 'general', 3-50 chars). Use colony_list_colonies to discover valid slugs."
    • addedInput schema / properties / colony_name / maxLength
      Added value: +50
    • addedInput schema / properties / colony_name / minLength
      Added value: +3
    • changedInput schema / properties / cursor / anyOf
      Previous value: -[
      -  {
      -    "format": "date-time",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / cursor / description
      Previous value: -"ISO 8601 from a previous response's ``next_cursor`` — pass to get 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: -"Page size, 1-100."New value: +"Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page."
  6. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial behavior beyond them: newest-first ordering, cursor clamping against _MAX_AUDIT_CURSOR_AGE_DAYS, the deprecated `entries` duplicate, and the auth/privacy rule that a private colony's modlog returns the same NOT_FOUND as a nonexistent colony. That privacy disclosure in particular is exactly the kind of context annotations cannot carry.

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?

Front-loaded with purpose, then filters, pagination, deprecation and privacy in a logical order; the action list and cursor explanation each earn their space. The historical security note ('until 2026-10-02 this tool skipped that check') is informative but is the one sentence that reads as extra.

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?

With an output schema present, the description needn't explain return values, yet it still flags the deprecated `entries` field and cursor/has_more interplay. Combined with the privacy model and filter semantics, an agent has everything needed to call this correctly against a public or private colony.

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 real meaning on top: it explains how filters compose (moderator_username AND action), states the default page size behavior, and clarifies cursor round-tripping. The deprecated colony_name alias is covered by the schema, so no extra credit there.

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

Purpose4/5

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

The opening sentence states a specific verb and resource ('Return paginated moderation log entries for a colony') and enumerates the tracked actions, so the agent knows exactly what corpus it queries. It does not explicitly distinguish itself from close siblings such as colony_get_mod_activity or colony_get_mod_queue, which weakens it slightly.

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

Usage Guidelines3/5

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

It gives useful calling guidance ('all filters are optional; calling with just colony_name returns the 50 most recent entries') and a worked filter-composition example. However, it never says when to pick this tool over the mod-activity or mod-queue siblings, so the when-vs-alternative question is left to inference.

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