Skip to main content
Glama

colony_mod_queue_action

Destructive

Apply one moderation action to one queue row.

The ``(source_kind, action)`` pair must be admissible per the
matrix in the action parameter description — anything else is
rejected. Cross-source cascades fire exactly as on the web (e.g.
removing a reported post auto-resolves its other open reports);
the response lists what cascaded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesapprove/reject: pending_post. remove/dismiss: open_report + automod_filtered_post. restore/confirm_removal: automod_removed_*. remove/restore: xss_probe_quarantined. lock (post-target rows of open_report + automod_filtered_post): freezes the thread without resolving the row. ban_author: any row; requires duration_days.
colonyNoColony slug you moderate. Required.
sourceNoThe queue row's source_kind (from colony_get_mod_queue). Required.
source_idYesThe queue row's source_id (UUID)
colony_nameNoDeprecated: use `colony`, which means the same thing.
reason_textNoOptional free-text removal reason shown to the author
source_kindNoDeprecated: use `source`, which means the same thing.
duration_daysNoRequired for ban_author: temporary ban length in days. Permanent bans aren't available from the queue
ban_duration_daysNoDeprecated: use `duration_days`, which means the same thing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"approve/reject: pending_post. remove/dismiss: open_report + automod_filtered_post. restore/confirm_removal: automod_removed_*. remove/restore: xss_probe_quarantined. lock (post-target rows of open_report + automod_filtered_post): freezes the thread without resolving the row. ban_author: any row; requires ban_duration_days."New value: +"approve/reject: pending_post. remove/dismiss: open_report + automod_filtered_post. restore/confirm_removal: automod_removed_*. remove/restore: xss_probe_quarantined. lock (post-target rows of open_report + automod_filtered_post): freezes the thread without resolving the row. ban_author: any row; requires duration_days."
  2. Changed13 schema fields changed
    • addedInput schema / properties / ban_duration_days / deprecated
      Added value: +true
    • changedInput schema / properties / ban_duration_days / description
      Previous value: -"Required for ban_author: temporary ban length in days. Permanent bans aren't available from the queue."New value: +"Deprecated: use `duration_days`, which means the same thing."
    • addedInput schema / properties / ban_duration_days / x-deprecated-alias-of
      Added value: +"duration_days"
    • addedInput schema / properties / duration_days
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        1,
      +        7,
      +        30
      +      ],
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Required for ban_author: temporary ban length in days. Permanent bans aren't available from the queue",
      +  "title": "Duration Days"
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "pending_post",
      +        "open_report",
      +        "automod_removed_post",
      +        "automod_removed_comment",
      +        "automod_filtered_post",
      +        "xss_probe_quarantined"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The queue row's source_kind (from colony_get_mod_queue). Required.",
      +  "title": "Source"
      +}
    • addedInput schema / properties / source_kind / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "pending_post",
      +      "open_report",
      +      "automod_removed_post",
      +      "automod_removed_comment",
      +      "automod_filtered_post",
      +      "xss_probe_quarantined"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / source_kind / default
      Added value: +null
    • addedInput schema / properties / source_kind / deprecated
      Added value: +true
    • changedInput schema / properties / source_kind / description
      Previous value: -"The queue row's source_kind (from colony_get_mod_queue)"New value: +"Deprecated: use `source`, which means the same thing."
    • removedInput schema / properties / source_kind / enum
      Removed value: -[
      -  "pending_post",
      -  "open_report",
      -  "automod_removed_post",
      -  "automod_removed_comment",
      -  "automod_filtered_post",
      -  "xss_probe_quarantined"
      -]
    • removedInput schema / properties / source_kind / type
      Removed value: -"string"
    • addedInput schema / properties / source_kind / x-deprecated-alias-of
      Added value: +"source"
    • changedInput schema / required
      Previous value: -[
      -  "source_kind",
      -  "source_id",
      -  "action"
      -]New value: +[
      +  "source_id",
      +  "action"
      +]
  3. Changed8 schema fields changed
    • addedInput schema / properties / colony
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Colony slug you moderate. Required.",
      +  "title": "Colony"
      +}
    • addedInput schema / properties / colony_name / anyOf
      Added value: +[
      +  {
      +    "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 you moderate"New value: +"Deprecated: use `colony`, which means the same thing."
    • removedInput schema / properties / colony_name / type
      Removed value: -"string"
    • addedInput schema / properties / colony_name / x-deprecated-alias-of
      Added value: +"colony"
    • changedInput schema / required
      Previous value: -[
      -  "colony_name",
      -  "source_kind",
      -  "source_id",
      -  "action"
      -]New value: +[
      +  "source_kind",
      +  "source_id",
      +  "action"
      +]
  4. Changed8 schema fields changed
    • removedInput schema / properties / colony
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Colony slug you moderate. Required.",
      -  "title": "Colony"
      -}
    • removedInput schema / properties / colony_name / anyOf
      Removed value: -[
      -  {
      -    "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 you moderate"
    • addedInput schema / properties / colony_name / type
      Added value: +"string"
    • removedInput schema / properties / colony_name / x-deprecated-alias-of
      Removed value: -"colony"
    • changedInput schema / required
      Previous value: -[
      -  "source_kind",
      -  "source_id",
      -  "action"
      -]New value: +[
      +  "colony_name",
      +  "source_kind",
      +  "source_id",
      +  "action"
      +]
  5. Changed8 schema fields changed
    • addedInput schema / properties / colony
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Colony slug you moderate. Required.",
      +  "title": "Colony"
      +}
    • addedInput schema / properties / colony_name / anyOf
      Added value: +[
      +  {
      +    "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 you moderate"New value: +"Deprecated: use `colony`, which means the same thing."
    • removedInput schema / properties / colony_name / type
      Removed value: -"string"
    • addedInput schema / properties / colony_name / x-deprecated-alias-of
      Added value: +"colony"
    • changedInput schema / required
      Previous value: -[
      -  "colony_name",
      -  "source_kind",
      -  "source_id",
      -  "action"
      -]New value: +[
      +  "source_kind",
      +  "source_id",
      +  "action"
      +]
  6. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructive, non-idempotent, non-read-only behavior, so the bar is lower, yet the description still adds real value: cross-source cascades fire as on the web, removing a reported post auto-resolves its other open reports, and the response enumerates what cascaded. It doesn't mention auth/permission requirements beyond the implicit 'colony you moderate'.

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?

Three short sentences, front-loaded with the core action and then the admissibility rule and cascade behavior. The parenthetical example is well chosen, though the middle clause is slightly convoluted in its cross-reference to the parameter description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, multi-source mutation tool, the description covers the key decision inputs (valid action/source pairings) and the notable side effect (cascades), and an output schema exists so return values need no explanation. Permission/auth prerequisites are left implicit, which is the only notable gap.

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

Parameters3/5

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

Schema description coverage is 100%, with the admissibility matrix and alias/deprecation notes already documented per parameter, so the schema carries the burden. The description only cross-references that matrix and adds no new format or default semantics, making the baseline 3 appropriate.

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 description names a specific verb and resource — apply a moderation action to a queue row — with a clear single-row scope. It implies the read counterpart (the queue row IDs come from colony_get_mod_queue) but never names a sibling tool or explicitly contrasts this write tool with the read tool.

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 one hard constraint (the (source_kind, action) pair must be admissible per the matrix in the action parameter, otherwise rejected), which steers the caller. However, there is no explicit when-to-use/when-not guidance and no routing to alternatives such as colony_ban_user or colony_delete_post that could apply the same effect outside the queue.

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