Skip to main content
Glama

actions-create

Create an action

Create an action that reviewers and rules can take. type sets what it does: a built-in type changes the item or author in Moderation API, and a custom type (ITEM_CUSTOM, AUTHOR_CUSTOM) only records the decision for the webhooks to deliver. Creating an action does not execute it.

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-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so the bar is lower. The description still adds real behavioral context beyond them: creating does not execute the action, built-in types mutate the item/author in Moderation API, and custom types only record the decision for webhook delivery. It omits return behavior and duplicate/name-collision handling.

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?

Two short paragraphs, front-loaded with the core operation and followed by the key semantic distinction. The only waste is the opening 'Create an action' restating the title verbatim before the substantive second sentence.

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 nested-object mutation with no output schema and no idempotency guarantee, the definition covers the essentials: what is created, what type does, and that nothing is executed. The well-annotated nested schema carries the field-level burden, so remaining gaps (response shape, duplicate handling) are minor rather than disqualifying.

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?

The top-level `request` parameter is undocumented, and the nested body fields carry their own schema descriptions. What the description adds is genuinely new meaning for `type`: which enum values cause a real state change versus a record-only custom decision, which the schema only labels as 'The type of the action.' Other fields (position, queueBehaviour, possibleValues) get no elaboration in the description.

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 gives a concrete verb and resource (create an action) and immediately defines what an action is for: 'reviewers and rules can take'. The type taxonomy (built-in vs ITEM_CUSTOM/AUTHOR_CUSTOM) sharpens the purpose further. It stops short of naming sibling tools like actions-update or actions-list, so differentiation is implied rather than explicit.

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 line 'Creating an action does not execute it' implicitly routes the agent to actions-execute for running an action, which is useful guidance. However, there is no explicit when-to-use/when-not statement, no mention of when to prefer actions-update, and no prerequisites such as project scoping or permissions. Usage is inferable but not stated.

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