Frontman for WordPress

wp_create_post

Destructive

Creates a new post or page. For a user-requested author task, resolve the account with wp_find_users; never guess IDs or choose an ambiguous match. Read back successful author assignment with wp_read_post. Returns the new post ID and permalink. Use wp_duplicate_post when the user asks to duplicate or clone an existing page so Elementor/post metadata is copied.

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_id": "<site_id>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "wp_create_post"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No	Optional permalink slug. WordPress sanitizes it and applies status-specific uniqueness. Empty allows an empty draft/pending slug; published posts derive one from the title. The persisted slug is returned in after.slug.
`tags`	No	Existing tag term IDs. Supplied arrays replace assignments; empty clears tags. Omit on update to preserve. Never creates terms. Read IDs with wp_read_post.
`title`	Yes	The post title.
`author`	No	Native WordPress account ID. Omit to use the current user. Requires author support; assigning another account requires edit_others_posts for this post type.
`status`	No	Initial post status.	draft
`content`	Yes	The post content as HTML or Gutenberg block markup.
`site_id`	Yes	The connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
`template`	No	Pages only: an available native page-template slug/file, or default to reset. Omit on update to preserve. Read the actual assignment in wp_read_post.template.
`post_type`	No	Post type slug.	post
`categories`	No	Existing category term IDs. Supplied arrays replace assignments; omit on update to preserve. Empty uses the WordPress default category for posts (and filtered default-category post types), except auto-drafts; otherwise clears. Never creates terms. Read IDs with wp_read_post.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the risk profile is covered. The description adds real operational context beyond that: author assignment requires edit_others_posts, ambiguous user matches must not be guessed, and the caller should read back to confirm. It stops short of describing what a failed create leaves behind or any rate/limit behavior.

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?

Four compact sentences, front-loaded with the core action and followed by the workflow caveats. Every sentence carries a distinct rule; the middle sentences are slightly crammed but none is filler.

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

Completeness5/5

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

Ten parameters with three required and no output schema, but the description explicitly states the return values ('the new post ID and permalink'), filling the gap the missing output schema creates. An agent has enough to call this correctly and to verify the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description still contributes cross-tool meaning the schema cannot: author IDs come from wp_find_users, and author/template assignments are verified through wp_read_post. It does not restate the replace-vs-preserve semantics of tags/categories, which the schema already handles well.

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?

Opens with a specific verb and resource: 'Creates a new post or page,' and the post_type parameter is echoed in the description. It also names the sibling it is NOT (wp_duplicate_post) so an agent can route between create and clone without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: resolve authors with wp_find_users rather than guessing IDs, verify assignment with wp_read_post, and switch to wp_duplicate_post when the request is to duplicate or clone. It states the when, the when-not, and the alternative, leaving nothing to inference.

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

All Frontman for WordPress tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.