Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp elementor get

wordpress_specialist_wp_elementor_get
Read-only

Fetch and JSON-decode a post's Elementor data tree into a plain array, and report whether the post was edited with Elementor.

Instructions

[UNIFIED] Fetch the parsed _elementor_data tree for a post. The companion strips WP's slashes and JSON-decodes server-side; the caller always sees a plain array. Returns edited_with_elementor: false if the post hasn't been opened in Elementor. Requires Airano MCP Bridge v2.13.0+.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safe-read profile, and the description does add real behavior: slashes are stripped and JSON decoded server-side so the caller always receives a plain array, and non-Elementor posts yield edited_with_elementor: false. However, it discloses nothing about error behavior when a post lacks meta, whether it requires authentication, or output size, and the important failure mode (empty vs false) is ambiguous. It adds useful context but does not fully specify behavior beyond the annotation.

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?

Three tightly packed sentences, front-loaded with purpose, then return-shape behavior, then the edge case and version prerequisite. No filler.

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?

Annotations cover safety and there is no output schema, so the return explanation is a bonus. But with zero schema description coverage, the description leaves the 'site' parameter and post_id format unexplained, which is a real gap for a tool that must be called with two required arguments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%: both 'site' and 'post_id' are bare and undocumented. The description only indirectly implies post_id via 'for a post' and says nothing at all about what 'site' expects (an ID, URL, or alias), so it fails to compensate for the schema gap on a two-parameter tool.

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?

The description states a specific verb and resource: fetch the parsed _elementor_data tree for a post. It clearly distinguishes a read from the sibling set/write operations (wp_elementor_set) and css rendering (wp_elementor_render_css), but never names those alternatives explicitly, and its 'edited_with_elementor' fallback overlaps with what wp_elementor_detect likely does.

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 only implied: it says what it fetches and what happens for non-Elementor posts, which hints you should call it before editing Elementor data. There is no explicit 'use this when...' statement, no guidance about when to prefer wp_elementor_detect or wp_blocks_get, and no prerequisites beyond the bridge version.

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