Skip to main content
Glama

mcp_get_action_scheduler

Inspect the Action Scheduler queue for a WordPress site: counts per status, past-due pending actions, and the 10 most recent failures with masked last log messages.

Instructions

Action Scheduler queue (WooCommerce emails, webhooks, PDF jobs): counts per status, past_due pending actions and the 10 most recent failures with their last log message (secret-masked). available:false when Action Scheduler is not loaded. cvrt-mcp-endpoints 1.16.0+.

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": {
      "site": "<site>"
    },
    "name": "mcp_get_action_scheduler"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so reasonably well: it discloses that log messages are secret-masked, that failures are capped at the 10 most recent, that available:false signals Action Scheduler not being loaded, and a plugin version requirement. It stops short of stating read-only-ness explicitly or any performance/rate considerations, but the diagnostic-read character is clear.

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?

A single dense sentence that front-loads the resource and then lists outputs before the caveats; nothing is padding. It is somewhat packed with parentheticals and version tail, but every clause carries information.

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?

There is no output schema, so the description appropriately spells out the return shape (counts, past-due items, failure samples with masked logs) and the unavailable case. Given a one-parameter read tool, an agent has nearly everything it needs to call and interpret it.

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?

Only one parameter (site) and schema description coverage is 100%, with the schema itself pointing to list_sites. The description adds nothing about the site argument, so this is the baseline case where structured data does the work.

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?

States a specific resource (Action Scheduler queue) and enumerates exactly what is reported: status counts, past-due pending actions, and the 10 most recent failures with last log message. The read/diagnostic nature is unmistakable and the 'get' vs 'run' sibling distinction is implicit in the name, but the description never explicitly contrasts itself with mcp_run_action_scheduler.

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?

No explicit when-to-use or when-not-to-use statement, and no alternative is named. Usage is only inferable from the content list (you use it when you want to inspect queued/failed jobs rather than trigger them), which leaves the agent to work out the boundary with mcp_run_action_scheduler on its own.

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

Deploy Server

Other Tools