Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

List media library items

elementor_list_media
Read-onlyIdempotent

Search the WordPress media library to return attachment IDs and URLs in the {id,url} shape required by Elementor image controls.

Instructions

Search the WordPress media library and get back attachment ids and URLs. Elementor image controls need both, in the shape {"id":123,"url":"https://..."}.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
siteNoConfigured site name. Omit to use the default site.
searchNo
perPageNo
mimeTypeNoFilter by MIME type, e.g. "image".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered without description help. The description adds genuine value by disclosing the return shape (id plus URL pairs), which matters since there is no output schema. It says nothing about pagination behavior, total counts, or result limits, so it stops short of rich behavioral context.

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?

Two short sentences with no filler. The core action and return format are front-loaded, and the Elementor rationale is stated once without repetition.

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?

With no output schema, the description does well to state that results are id/url pairs. However, for a 5-parameter search tool with 40% schema coverage, it leaves search syntax, MIME filtering, and pagination unexplained, so an agent cannot fully predict query behavior from the definition alone.

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 only 40%: site and mimeType are documented in the schema, while search, page, and perPage are bare. The description mentions searching but never explains the search parameter, MIME filtering, or paging, so it fails to compensate for the coverage gap on 3 of 5 parameters.

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: search the WordPress media library and return attachment IDs and URLs. It also names the consumer (Elementor image controls) and the exact shape they require, which makes the tool's output purpose unambiguous. It does not explicitly contrast with sibling list tools, which keeps it from a 5.

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 implied by the mention that Elementor image controls need id/url pairs, so an agent can infer this is the lookup step before setting an image. There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named for cases like listing pages or templates.

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