Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Upload an image from a URL

elementor_upload_image

Downloads a remote image into the WordPress media library and returns the attachment ID, URL, and a value ready for Elementor image controls, which require library attachments rather than remote URLs.

Instructions

Download a remote image into the WordPress media library and return the attachment id and URL, plus a ready-made value for an Elementor image control. Use this before setting any image setting — Elementor image controls want a library attachment, not a remote URL.

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": {
      "url": "<url>"
    },
    "name": "elementor_upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the image to fetch.
siteNoConfigured site name. Omit to use the default site.
titleNo
altTextNoAlt text. Worth setting for accessibility and SEO.
attachToPostIdNoAttach the upload to this post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the safety profile is covered; the description still adds real value by disclosing the concrete side effect (the image lands in the media library) and the shape of the result, including a ready-made Elementor control value. It is silent on duplicate handling, size or format limits, and what happens on fetch failure, which are meaningful gaps for a remote-fetch mutation.

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 sentences, both earning their place: the first establishes action and return value, the second establishes prerequisites and the reason for them. The prerequisite is placed where an agent will read it before forming the call.

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?

There is no output schema, and the description compensates by describing the return value (attachment id, URL, Elementor control value). Combined with 80% schema coverage, an agent has enough to invoke it correctly, though error and duplicate-handling behavior are unaddressed.

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 80%, so the schema already documents url, site, altText, and attachToPostId. The description adds no parameter-level meaning beyond that — nothing about what site selection does to the returned URL or when attachToPostId matters. Baseline 3 applies when structured fields carry the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb chain (download a remote image) and destination (WordPress media library), and states what is returned (attachment id, URL, Elementor control value). That makes it unmistakable against siblings such as elementor_list_media, which only enumerates existing media.

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?

"Use this before setting any image setting" gives an explicit precondition and explains why (Elementor image controls want a library attachment, not a remote URL), which effectively rules out passing remote URLs directly. It does not say what to do if the image already exists in the library, so the reader is left to infer whether a list_media check precedes this call.

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