Skip to main content
Glama
Sign In
wordpress-mcp

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mcp_get_elementor_conditions

Retrieve theme builder display conditions for an Elementor template. Use it to check where a template applies before editing.

Instructions

Get theme builder display conditions for an Elementor template

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>",
      "id": "<id>"
    },
    "name": "mcp_get_elementor_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTemplate post ID
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: -[
-  "id"
-]New value: +[
+  "site",
+  "id"
+]
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a safe read, but the description does not say whether it requires a theme-builder template, what shape the conditions take, or anything about failure modes; it also omits any return description, and no output schema compensates.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though almost too terse given the absence of supporting structured data (annotations, output 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 two-parameter getter with full schema coverage, the description is minimally viable, but with no annotations and no output schema it should do more: it never clarifies what 'display conditions' are, what template types are valid, or what the caller receives. Adequate rather than complete.

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%: id is documented as 'Template post ID' and site as 'Site id (see list_sites)', including the cross-reference to list_sites. The description adds nothing beyond the schema, so the 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 (Get) and a specific resource (theme builder display conditions for an Elementor template), which is meaningfully distinct from siblings like mcp_get_elementor_build, mcp_get_elementor_flat, and mcp_get_elementor_page_settings. It does not explicitly name those siblings, but the resource noun is unique enough that an agent can differentiate.

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?

There is no guidance on when to call this versus the nearby Elementor getters (build/flat/element/page settings/kit), and no prerequisites mentioned beyond what the schema's required fields imply. The purpose alone lets the reader infer it is a read, but no exclusions or routing context is provided.

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