Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_elementor_get_element

Read-onlyIdempotent

Gets one Elementor element by post_id and element_id. Selected Elementor elements include these IDs in the selected-element context.

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_id": "<site_id>",
      "post_id": "<post_id>",
      "element_id": "<element_id>"
    },
    "name": "wp_elementor_get_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesWordPress post/page ID.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
element_idYesElementor element ID from page structure or selected-element context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered structurally. The description adds the useful detail that element IDs surface in the selected-element context, but says nothing about what is returned (rendered HTML vs. element settings) or behavior for unknown element IDs.

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 sentences, front-loaded with the operation and identifiers, with no filler. It is efficient but thin enough that the second sentence only partially earns its place by echoing the schema's element_id hint.

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 simple read-only getter with full schema coverage and complete annotations, most call requirements are satisfied. However, with no output schema, the description should say what a returned element contains and how to interpret a missing element, and it does not.

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%, including the site_id warning to call list_sites first and the note that element_id comes from page structure or selected-element context. The description largely restates the schema's element_id provenance rather than adding new meaning, so baseline 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 ("Gets one Elementor element") plus the two identifiers that scope it, so an agent knows it retrieves a single element rather than a page or structure. It does not distinguish itself from siblings such as wp_elementor_get_page_structure or wp_elementor_get_page_data, which get whole-page data.

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 explicit when-to-use guidance beyond the retrieval verb; it never says to prefer wp_elementor_get_page_structure when many elements are needed, nor states any prerequisite such as having the post loaded. The only hint is that element IDs appear in the selected-element context, which implies but does not state usage conditions.

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources