Skip to main content
Glama

create_post

Create a new WordPress post with title and content, defaulting to draft status to prevent accidental publication.

Instructions

Create a new WordPress post (basic). Defaults to draft status so nothing is published unintentionally.

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoURL slug (optional). If omitted, WordPress generates one from the title (a Japanese title gives a Japanese slug). Use it to set an ASCII slug, e.g. 'my-first-post'. WordPress may change it (for example, appending '-2' if the slug is already used); the result shows the actual slug
titleYesThe post title
statusNoPost status. Defaults to 'draft' to avoid accidental publication.draft
contentYesThe post content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, non-idempotent, and closed-world, so the mutation profile is covered. The description usefully restates the safety default ('draft so nothing is published unintentionally'), but adds nothing about the consequences of the non-idempotent flag — e.g. that calling twice creates duplicate posts — nor about required capabilities or what is returned.

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 sentence plus one clause, both front-loaded: what it does first, safety behavior second. Nothing is wasted and nothing is buried.

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?

For a create tool with no output schema, the description omits what the caller gets back (post ID, actual slug, status) — the slug parameter notes 'the result shows the actual slug', but that fact lives in the schema, not the description. Adequate given strong annotations and full schema coverage, but not fully complete for a four-parameter mutation tool.

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?

Schema description coverage is 100%, including a detailed slug explanation and an enum with default for status, so the schema carries parameter meaning fully. The description adds only the draft-default fact, which already appears in the status parameter description; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Create a new WordPress post') and the parenthetical '(basic)' signals it is the simple variant among several create_post_* siblings. It never names those siblings explicitly (e.g. create_advanced_post), so the differentiation is suggested rather than stated.

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 'basic' qualifier and the safe draft default, which tells an agent this is the low-risk entry point. There is no explicit when-to-use / when-not-to-use guidance pointing at create_advanced_post, create_post_with_categories_tags, or create_post_with_featured_image.

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