Skip to main content
Glama

update_post

DestructiveIdempotent

Modify an existing WordPress post or page by ID, including title, content, status, slug, categories, tags, featured image, and publication date.

Instructions

Update an existing WordPress post or page

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": {
      "post_id": "<post_id>"
    },
    "name": "update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoPublication date (optional, ISO8601 in the site's time zone, e.g. '2026-11-19T10:00:00'). With status 'future' and a future date, the post is scheduled. get_post shows the current date
slugNoNew URL slug (optional, e.g. an ASCII slug for a post with a Japanese title). WordPress does not update the slug when the title changes. Changing the slug of a published post changes its URL
tagsNoArray of tag IDs (optional)
titleNoNew post title (optional)
statusNoPost status (optional): 'publish', 'draft', 'pending', 'private', or 'future' (scheduled; needs 'date' unless the post is already scheduled)
contentNoNew post content (optional)
post_idYesPost or page ID to update
post_typeNoContent type being updated. Defaults to 'post'.post
categoriesNoArray of category IDs (optional)
featured_media_idNoFeatured image media ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond them: it does not say whether omitted fields are left untouched or cleared, what happens to a published post when status changes, or what permissions are required. For a destructive mutation with 10 parameters, that is a real gap.

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?

One short sentence with no wasted words and the resource front-loaded. It is lean to the point of under-specification, but nothing in it is redundant or padded.

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?

For a destructive, ten-parameter mutation with no output schema, the description leaves the agent to infer partial-update semantics, side effects on published URLs, and scheduling behavior entirely from the schema. The schema is rich, but the description itself contributes almost nothing an agent needs before invoking it.

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%, so every parameter including scheduling via status 'future' plus date, slug/URL implications, and category/tag ID arrays is already documented in the schema. The description adds no meaning beyond that, so the baseline of 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?

States a specific verb and resource: 'Update an existing WordPress post or page.' That distinguishes it from create_post, delete_post, and get_post by verb alone. It does not distinguish it from sibling mutators like update_post_categories_tags or update_media, but the resource noun carries most of that work.

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?

No when-to-use guidance, no prerequisites, and no alternatives are named. The description never tells an agent when to reach for update_post_categories_tags instead, or that get_post should be read first to obtain current values before a partial update.

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