Skip to main content
Glama

mcp_update_cpt_post

Update a WordPress post of any type by changing only specified fields and merging meta key-values, preserving existing content and metadata.

Instructions

Update a post of any post type. Only the given fields change; meta keys are merged (update_post_meta per key).

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": "<site>",
      "type": "<type>",
      "id": "<id>"
    },
    "name": "mcp_update_cpt_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID
metaNoPost meta key-value pairs to set
siteYesSite id (see list_sites)
typeYesPost type name (e.g. post, page, product, testimonial)
titleNoPost title
statusNoPost status
contentNoPost content. Note: the endpoint sanitizes it as plain text, so HTML tags are stripped

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.14.0
    • changedInput schema / properties / content / description
      Previous value: -"Post content"New value: +"Post content. Note: the endpoint sanitizes it as plain text, so HTML tags are stripped"
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / meta / description
      Previous value: -"Post meta key-value pairs"New value: +"Post meta key-value pairs to set"
    • addedInput schema / properties / status / enum
      Added value: +[
      +  "publish",
      +  "future",
      +  "draft",
      +  "pending",
      +  "private"
      +]
    • changedInput schema / properties / type / description
      Previous value: -"Post type name"New value: +"Post type name (e.g. post, page, product, testimonial)"
    • addedInput schema / properties / type / pattern
      Added value: +"^[a-zA-Z0-9_-]+$"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "type",
      -  "id"
      -]New value: +[
      +  "site",
      +  "type",
      +  "id"
      +]
  3. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses partial-update semantics and that meta keys are merged via update_post_meta per key, which the schema does not say. It omits permission/auth requirements, what happens to meta keys not listed, and error behavior for invalid ids or status transitions.

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?

Two short sentences, front-loaded with the operation and followed by the mutation semantics; there is no filler and nothing redundant with the schema.

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 7-parameter mutation tool with no annotations and no output schema, the definition covers update semantics but leaves the agent without permission requirements, failure modes, or any hint of the response shape. It is minimally viable rather than complete.

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, but the description adds real meaning by clarifying that unspecified fields are left untouched and that meta is merged per key rather than replaced wholesale. That resolves the main ambiguity in the 'meta' object parameter.

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?

"Update a post of any post type" gives a specific verb (update) and resource (post), plus a scope qualifier (any post type) that separates it from the type-specific siblings. It does not name a sibling to differentiate against, so it stops short of a 5.

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 description implies when to use it (partial modification of an existing post) and signals that only supplied fields change, but it never states when to prefer this over wp_update_post or acf_update_post_field(s), nor any preconditions such as the post needing to exist.

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

Deploy Server

Other Tools