Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp cron list

wordpress_specialist_wp_cron_list
Read-only

List WordPress cron events with hook names, next-run times, schedule slugs, intervals, and stored args to inspect scheduled tasks and diagnose cron behavior.

Instructions

[UNIFIED] Dump the WordPress cron table: hook name, next run time (epoch + ISO 8601 UTC), schedule slug, interval, and stored args. Requires Airano MCP Bridge v2.11.0+ and manage_options.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with that. It adds value beyond the annotations by naming concrete prerequisites the agent must satisfy before calling: Airano MCP Bridge v2.11.0+ and the manage_options capability. It does not describe failure modes or how large cron tables are handled, so it falls short of a 5.

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?

Two sentences, front-loaded with the action and payload, followed by the prerequisites. No filler and no repetition of the tool name beyond the bracketed '[UNIFIED]' marker.

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?

With no output schema, the description compensates well by enumerating the returned fields and their formats (epoch + ISO 8601 UTC). Prerequisites are covered. The missing piece is any explanation of the sole 'site' parameter and of behavior on very large cron tables, which keeps it from a 5.

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 single required parameter 'site' is never explained in the description. The agent must guess the expected format (site slug, ID, or URL) from the name alone, which is a real gap even for a one-parameter tool.

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?

States a specific verb ('Dump') and resource ('the WordPress cron table') and then enumerates exactly what each row contains: hook name, next run time in epoch and ISO 8601 UTC, schedule slug, interval, stored args. An agent can tell this is a read-only inspection of scheduled cron events, distinct from the sibling list/get tools for menus, options, or permalinks.

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?

Usage is implied by the read-only 'dump' framing plus the manage_options prerequisite, which tells the agent this is an admin-level inspection call. However, there is no explicit statement of when to choose this over alternatives (e.g., db_search or maintenance_status) and no when-not guidance or mention of pagination/limits, so the agent must infer the context.

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