Skip to main content
Glama

actions-list

Read-only

List moderation actions

List the moderation actions of the project, with their webhooks. An action is a decision that a reviewer or a rule can take on content or an author. Built-in actions (for example reject an item or block an author) change the item or author in Moderation API. Custom actions record the decision and send it to the webhooks of the action, where the customer platform acts on it. The list is paginated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "actions-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine value by explaining that built-in actions mutate the item/author in Moderation API while custom actions only record and fan out to webhooks, and that results are paginated, but it does not describe page-size limits, ordering, or default page size beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded and reasonably short, but the lead line is duplicated almost verbatim in the second sentence, and the built-in/custom action explanation consumes space that could have carried parameter or pagination guidance. No wasted formatting, but the allocation of words is suboptimal.

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

Completeness3/5

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

There is no output schema, so the description carries some burden for describing return contents, which it partly does by stating each action comes with its webhooks. However, for a paginated list tool with a nested request object and undocumented filter parameters, it stops short of telling an agent how to page through results or what a queueId filter does.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only hints at pagination ("The list is paginated") without explaining page, pageSize, or queueId semantics. The one well-documented parameter, projectId, is documented inside the schema rather than the description, so the description does not compensate for the coverage gap on the filter parameters.

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 ("List the moderation actions of the project, with their webhooks") and clarifies the domain object ("an action is a decision that a reviewer or a rule can take on content or an author"). This clearly separates it from actions-create/update/execute/retrieve by verb, though it does not explicitly name the singular retrieve sibling.

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?

Listing is self-evidently for enumerating actions, so the use case is implied, but there is no explicit guidance on when to call this versus actions-retrieve, nor any mention of narrowing by queueId or projectId. The built-in vs custom action explanation describes the domain rather than when to use this tool.

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