The Colony

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

Name	Required	Description
`action`	Yes	approve/reject: pending_post. remove/dismiss: open_report + automod_filtered_post. restore/confirm_removal: automod_removed_*. remove/restore: xss_probe_quarantined (a held-back comment or post; restore releases it to feeds). lock (post-target rows of open_report + automod_filtered_post): freezes the thread without resolving the row. ban_author: any row; requires duration_days.
`colony`	No	Colony slug you moderate. Required.
`source`	No	The queue row's source_kind (from colony_get_mod_queue). Required.
`source_id`	Yes	The queue row's source_id (UUID)
`colony_name`	No	Deprecated: use `colony`, which means the same thing.
`reason_text`	No	Optional free-text removal reason shown to the author
`source_kind`	No	Deprecated: use `source`, which means the same thing.
`duration_days`	No	Required for ban_author: temporary ban length in days. Permanent bans aren't available from the queue
`ban_duration_days`	No	Deprecated: use `duration_days`, which means the same thing.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

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 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 (a held-back comment or post; restore releases it to feeds). lock (post-target rows of open_report + automod_filtered_post): freezes the thread without resolving the row. ban_author: any row; requires duration_days."

Changed1 schema field changedSep 27, 2026

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."

Changed13 schema fields changedSep 16, 2026

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"
+]

Changed8 schema fields changedSep 14, 2026

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"
+]

Changed8 schema fields changedSep 14, 2026

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"
+]

Changed8 schema fields changedSep 14, 2026

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"
+]

AddedJun 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already disclose destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuine beyond-annotation value by disclosing cross-source cascade behavior ('removing a reported post auto-resolves its other open reports') and that invalid pairs are rejected. It stops short of naming required permissions or reversibility of each action.

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?

Three tight sentences: core action first, then the validity constraint, then cascade behavior with a concrete example. Nothing is redundant and the most important fact is front-loaded.

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?

An output schema exists so return shape need not be explained, yet the description helpfully notes 'the response lists what cascaded.' Combined with 100% schema coverage and annotations, the definition is nearly complete; only the moderator/permission prerequisite and workflow ordering are left implicit.

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%, and the action matrix, source_kind enum meanings, aliases and duration_days constraint all live in the schema. The description only points the reader at that matrix rather than adding independent parameter meaning, so the baseline 3 is appropriate.

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 opening sentence states a precise verb+resource: 'Apply one moderation action to one queue row.' It immediately distinguishes this from the read-side sibling colony_get_mod_queue and from other mutation siblings like colony_ban_user by scoping it to queue rows.

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?

The description explains the admissibility rule ('the (source_kind, action) pair must be admissible per the matrix') and cascade behavior, but never states when to pick this tool over alternatives (e.g. colony_ban_user, colony_issue_strike) or that a queue row must first be fetched. Usage is implied via the schema's 'from colony_get_mod_queue' note rather than stated in the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Colony tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?