wp-ssh-mcp

Overview Schema Source Related Servers Discussions Admin

elementor_data_get

elementor_data_get

Read-onlyIdempotent

Fetch the raw _elementor_data JSON for a WordPress page by post ID to inspect or export Elementor layout data, even when the payload is large.

Instructions

Raw _elementor_data JSON of a page. Can be very large.

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": "elementor_data_get"
  }
}

Input Schema

Name	Required	Description	Default
`post_id`	Yes	Post ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds one genuinely useful behavioral fact, that the payload can be very large, but says nothing about whether the return is a raw string vs parsed object, or about permissions on the Elementor data.

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?

Two short, front-loaded sentences with no filler, and the size warning sits where a caller will see it before invoking. It is efficient, though borderline under-specified rather than truly tight.

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?

Adequate for a one-parameter read tool whose annotations cover safety, but an agent gets no hint about the shape of the payload, whether the large JSON is returned as a string, or what happens for a page with no Elementor data.

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 100% with a single post_id parameter, so the schema does the documenting and baseline 3 applies. The description adds a small amount by clarifying the target is a page, slightly narrowing what post_id can refer to.

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 resource and verb-like action: returns the raw _elementor_data JSON for a given page. The resource is precise, but it never distinguishes itself from sibling readers like post_get, file_read, or db_query, so an agent must infer why this getter exists.

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 at all. The only conditional hint is 'Can be very large', which warns about output size but doesn't say when to prefer this over post_get or db_query, or what to do instead when the payload is big.

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