AutoWP MCP Server

schedule-post

Schedule a WordPress post to publish at a future date by providing the post ID and ISO 8601 timestamp.

Instructions

Schedule a WordPress post for future publication

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": {
      "postId": "<postId>",
      "publishDate": "<publishDate>"
    },
    "name": "schedule-post"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	ID of the post to schedule
`publishDate`	Yes	Publication date/time in ISO format (e.g., '2024-12-25T10:00:00')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral details on its own. It does not mention side effects such as changing post status to 'scheduled', validation of the date, or what happens if the date is in the past. This is a significant gap for a mutation tool.

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?

A single, front-loaded sentence that conveys the purpose without any filler. Every word carries meaning, making it highly concise and well-structured.

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

Completeness2/5

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

Despite being a simple tool, it lacks an output schema and has no annotations. The description does not explain what happens on success or failure, nor does it clarify prerequisites like authentication (though sibling authenticate-wp exists). It provides only the bare minimum, leaving the agent guessing about expected outcomes and edge cases.

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?

Both parameters are fully described in the input schema (100% coverage), so the baseline is 3. The description itself adds no additional meaning beyond the schema, correctly avoiding redundancy but not enriching parameter understanding.

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 uses a specific verb 'Schedule' with a clear resource 'WordPress post' and the intent 'for future publication'. This clearly distinguishes it from sibling tools like update-post or create-blog-post, which address immediate changes or creation.

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 phrase 'for future publication' implies the tool is used when a post is intended to be published later, but no explicit guidance is given about when not to use it or which alternatives (e.g., update-post) might be more appropriate. The usage is inferred rather than clearly stated.

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