Skip to main content
Glama

create_advanced_post

Create WordPress posts or pages with control over status, scheduling, slug, categories, tags, featured image, and SEO meta fields.

Instructions

Create a new WordPress post or page with advanced 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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_advanced_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoPublication date (ISO8601 format, required for 'future' status)
metaNoMeta fields for SEO (e.g., _yoast_wpseo_metadesc, _yoast_wpseo_meta-robots-noindex, _yoast_wpseo_meta-robots-nofollow)
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
tagsNoTag IDs (posts only)
titleYesThe post/page title
statusNoPost status: 'publish' (公開), 'draft' (下書き), 'pending' (レビュー待ち), 'private' (非公開), 'future' (予約投稿、'date'が必須). Defaults to 'draft' so nothing is published unintentionally.draft
contentYesThe post/page content
post_typeNoPost type: 'post' (投稿) or 'page' (固定ページ)post
categoriesNoCategory IDs (posts only)
featured_media_idNoFeatured image media ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description adds nothing beyond that: no mention of required capabilities, whether the default draft status prevents accidental publishing, or that the operation is non-idempotent and will create duplicates on retry.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity comes at the cost of the specificity noted elsewhere.

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?

This is a 10-parameter mutation tool with a nested meta object and no output schema. The description says nothing about what gets created, how the nested meta fields behave, or what the response returns, leaving the agent to infer everything from the schema.

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 enum documentation for status and post_type and detailed notes on slug and meta, so the schema carries the parameter burden. The description itself contributes no parameter meaning, which is the expected baseline when coverage is this high.

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

Purpose3/5

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

The description states a concrete verb and resource ("Create a new WordPress post or page"), but the qualifier "with advanced options" is vague and does nothing to separate it from the numerous sibling creators such as create_post, create_post_with_categories_tags, create_post_with_embeds, and create_post_with_featured_image. An agent cannot tell from the text which creator to pick.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusion of alternatives, and no prerequisites mentioned. The crowded sibling set of near-identical create_post_* tools makes this omission especially costly.

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