wordpress_schedule_eventSchedule a new WordPress cron event for one-time or recurring execution. Define the hook name to trigger actions at specific times.
Schedule a new cron event (one-time or recurring)
| Name | Required | Description | Default |
|---|---|---|---|
| hook | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action itself and does not disclose side effects, required permissions, duplicate behavior, or how recurrence is expressed. The phrase 'one-time or recurring' is the only behavioral hint but is too vague.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, direct and front-loaded, with no filler words. It earns its place, though the extreme brevity borders on under-specification, which is a completeness concern rather than a conciseness concern.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, no annotations, and a minimal description, the agent lacks critical details about the hook parameter, recurrence settings, and expected result. It is not complete enough for correct invocation despite the tool's conceptual simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter, `hook`, with no description and schema coverage at 0%. The description never mentions `hook` or explains accepted values or how to indicate one-time vs recurring, leaving the agent unable to construct a valid invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it schedules a new cron event and mentions one-time or recurring, distinguishing it from sibling tools that list, unschedule, run, or get cron schedules. It also differentiates from wordpress_schedule_post, which schedules posts rather than cron events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides no guidance on when to use this tool vs alternatives like wordpress_schedule_post, wordpress_list_cron_jobs, or wordpress_unschedule_event. No context or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.