Skip to main content
Glama

media_eio_run

Imports Elementor Image Optimizer results: optimized sizes become Media records, original links are rewritten to current files, originals move to backup; requires confirm:true after a dry run.

Instructions

Import Elementor Image Optimizer's work (no re-encoding): its optimized sizes become [cvrt] Media records, links to its originals are rewritten to the current files, and its originals move into the backup store, up to limit attachments per call (repeat until done, each step is resumable). Changes records, content links and files on the site; run media_eio_dry_run first. Needs confirm: true, otherwise the site refuses with 400.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
limitNoMost attachments adopted in this call, 1..500
confirmNoMust be true for the action to run; anything else makes the site refuse it with 400

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses that records, content links and files on the site are all mutated, that originals are preserved in a backup store (implying recoverability), that execution is chunked and resumable, and that a missing confirm yields a 400 refusal. These are exactly the traits an agent needs before firing a destructive import.

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?

Three sentences, front-loaded with the outcome and followed by the safety prerequisite, with no filler. It is dense to the point of being hard to parse on first read, and the opaque '[cvrt]' token adds decoding cost without adding information.

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 mutating, resumable bulk import with no output schema, the description covers side effects, safety gating, batching and recoverability, which is nearly everything an agent needs. It omits what the call returns (e.g. how many attachments were adopted and whether more remain), which matters for a tool designed to be looped.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by tying 'limit' to the resumable-batch workflow ('up to limit attachments per call, repeat until done'), which explains the parameter's role rather than restating its range. The confirm explanation largely duplicates the schema's own wording, so it is not a full 5.

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?

States a specific verb and resource ('Import Elementor Image Optimizer's work') and enumerates the three concrete outcomes: optimized sizes become Media records, links are rewritten, originals move to the backup store. It also distinguishes itself from the sibling by naming 'media_eio_dry_run' as the non-mutating counterpart, so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly prescribes the sequence ('run media_eio_dry_run first') and the iteration model ('repeat until done, each step is resumable'), plus the prerequisite 'Needs confirm: true'. It names the alternative tool and the condition selecting it, leaving little to inference.

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