Skip to main content
Glama

actions-execute

Destructive

Execute moderation action

Execute one action of the project, by ID or key, on content items or authors. A built-in action changes them in Moderation API (for example rejects the items or blocks the authors). Every executed action is recorded, and the project sends it to the webhooks of the action and to its other webhook endpoints, where the customer platform can act on it. List the actions first to see what each one does.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "actions-execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description adds substantive behavior beyond them: built-in actions mutate state in Moderation API, every execution is recorded, and the project fans the action out to the action's webhooks and other webhook endpoints. What is missing is what happens on partial failure (some IDs valid, some not) or whether execution is atomic across multiple content/authors.

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 content is front-loaded and informative, with scope first and side effects second. The only waste is the opening line 'Execute moderation action,' which merely restates the annotation title before the substantive sentence begins.

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, non-idempotent, open-world mutation with nested parameters and no output schema, the description covers what it does, what state changes, and the webhook fan-out a caller must anticipate. The remaining gap is the overlap with the dedicated allow/reject/block siblings and any error or partial-success semantics.

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?

The top-level 'request' object carries no schema description, so the description has to compensate, and it does only partially: it clarifies that the action may be addressed by 'ID or key' and that targets are 'content items or authors,' matching contentIds/authorIds. It says nothing about the roles of value, duration, queueId, moderator, or createCasebookCase, leaving the nested schema descriptions to carry the rest.

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 names a specific verb (execute) and resource (one moderation action, by ID or key) and states the target domain (content items or authors). It is clearly distinguishable from actions-list, actions-retrieve, actions-create, and actions-delete because it is the only one that applies an action.

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?

There is a useful prerequisite instruction: 'List the actions first to see what each one does,' which pushes the agent to actions-list before calling. However, the description never explains when to use this generic action executor instead of the dedicated siblings content-reject, content-allow, authors-block, or authors-suspend, which overlap heavily with built-in actions.

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