Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_cron_events

Display all scheduled WordPress cron events with their hooks and schedule times, enabling you to review and diagnose cron-related issues.

Instructions

List scheduled WordPress cron events (read-only)

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": "wp_list_cron_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNoFilter by cron hook name
pageNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A3.8/5.0
Behavior4/5

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

There are no annotations, so the description carries the full burden. Explicitly stating '(read-only)' is a meaningful behavioral disclosure that signals no state changes. It does not go further into pagination behavior or response details, but for a simple list operation the read-only guarantee is the key behavioral fact.

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?

One short, front-loaded sentence with no filler. Every word earns its place, and the read-only qualifier is included without bloating the text.

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?

Adequate for a simple list operation, but there are gaps: no output schema, no clarification of hook filter behavior, and no pagination semantics. The agent can call it with zero parameters, but would lack details about response shape and filter matching when using the optional parameters.

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 only 33%, with only 'hook' explained. The description adds no parameter-level meaning; 'page' and 'per_page' are left to their names and numeric constraints. Because coverage is low, the description should have compensated, but it does not.

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 ('List'), a specific resource ('scheduled WordPress cron events'), and immediately disambiguates it from the many other wp_list_* sibling tools. An agent can tell this apart from wp_list_pages, wp_list_posts, or wp_list_themes without opening the schema.

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 implies the tool is for reading scheduled cron events but provides no explicit when-to-use or when-not-to-use guidance. It does not name alternatives or state exclusions, so an agent has to infer the use case from the name and description.

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