Skip to main content
Glama

royal-mcp__elementor_list_local_templates

Read-onlyIdempotent

[Also available: elementor/build-composition, elementor/get-page-structure via Elementor's native MCP.] Enumerate saved templates from the Elementor Library (the elementor_library custom post type). Returns id, name, type (page/section/widget/popup/etc.), and date_modified for each. Filter by type or by words in the title if needed. Use this before elementor_import_template to discover available templates. (site: demo.royalplugins.com) Through Royally: read-only, runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "royal-mcp__elementor_list_local_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional filter by template type (page, section, widget, popup, header, footer, single, archive)
limitNoMax templates to return (default 50, max 200)
titleNoOptional: only templates whose title contains this text (not case-sensitive).
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max templates to return (default 50)"New value: +"Max templates to return (default 50, max 200)"
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "Optional: only templates whose title contains this text (not case-sensitive).",
      +  "type": "string"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'read-only, runs straight away' largely restates them. What the description genuinely adds is the response shape (id, name, type, date_modified) and the source of truth (the elementor_library custom post type), which matters because there is no output schema. No pagination or truncation behavior is described beyond what the schema's limit field implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and return fields are front-loaded and useful, but the definition is padded: the bracketed '[Also available: elementor/build-composition, elementor/get-page-structure ...]' cross-promo and the inline '(site: demo.royalplugins.com)' duplicate information already present in the site_id enum and add noise for an agent selecting the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple filtered-list tool with no output schema, the definition supplies what an agent needs: data source, returned fields, filter options, and the downstream workflow with elementor_import_template. Only minor gaps remain, such as what happens when the limit is exceeded or whether results are ordered.

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%, so every parameter (type, limit, title, site_id) is already documented in the schema. The description restates 'filter by type or by words in the title' but adds no format, matching, or default semantics beyond that. Baseline 3 is appropriate when the schema carries the burden.

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 gives a specific verb and resource — 'Enumerate saved templates from the Elementor Library (the elementor_library custom post type)' — and names the exact fields returned, so the agent knows precisely what comes back. It does not explicitly contrast itself with the sibling royal-mcp__wp_list_block_templates, but the 'Elementor Library / elementor_library' scoping is specific enough to separate them in practice.

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?

It provides clear workflow context: 'Use this before elementor_import_template to discover available templates', which tells the agent where this tool sits in a sequence. Filtering guidance ('Filter by type or by words in the title if needed') is also given, though there is no explicit statement of when NOT to use it or which sibling to prefer for block/pattern listings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources