Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Update page metadata

elementor_update_page_meta
Idempotent

Updates a WordPress page's title, slug, status, parent, or featured image by post ID, letting you manage post fields while leaving the Elementor layout untouched.

Instructions

Change a page's title, slug, status, parent or featured image. This edits WordPress post fields, not the Elementor layout — use the element tools for that.

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": {
      "postId": "<postId>"
    },
    "name": "elementor_update_page_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
slugNo
titleNo
parentNo
postIdYesWordPress post ID of the Elementor page, post or template.
statusNo
postTypeNoREST base of the post type: "pages", "posts", or a custom type's rest_base.pages
featuredMediaIdNoAttachment ID to use as featured image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful scope information — it mutates WordPress post fields, not the Elementor layout — but omits partial-update semantics (are omitted fields preserved?), status-transition consequences, and whether the page must exist as an Elementor page.

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 sentences, front-loaded with the mutation surface and followed by the disambiguation clause. No filler, no repetition of the title.

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?

With 8 parameters, half undocumented, no output schema, and an idempotent write that can publish live content, the description is thinner than the tool's complexity warrants. It covers scope but not write semantics, required-vs-optional behavior, or return information.

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 coverage is only 50%, and the description largely restates the field names already present in the schema (title, slug, status, parent, featuredMediaId). It adds no meaning for postType, site, or postId, and gives no hint that featuredMediaId expects an attachment ID resolvable via elementor_list_media or that status changes affect page visibility.

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?

States a specific verb (change) and resource (page metadata) and enumerates the exact fields affected: title, slug, status, parent, featured image. It also explicitly demarcates the boundary from the element tools, so an agent can distinguish it from elementor_update_element without reading any schema.

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

Usage Guidelines4/5

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

The second sentence gives an explicit when-not and points to the alternative family (element tools). However, no alternative is named for closely related sibling operations like elementor_create_page or elementor_update_element individually, and there is no guidance on prerequisites such as fetching current values or the effect of flipping status to publish.

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