Skip to main content
Glama

media_eio_cleanup

Deletes Elementor Image Optimizer leftover metadata and image_optimizer_* options after migration, requiring confirm: true to prevent accidental data loss.

Instructions

Delete Elementor Image Optimizer's leftover metadata and image_optimizer_* options once the migration is complete (the site answers 409 while EIO is active or imports are pending). DESTRUCTIVE: the deleted EIO data cannot be recovered; [cvrt] Media records and backups stay. 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_cleanup"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
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

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does well: it flags DESTRUCTIVE, states the deleted EIO data is unrecoverable, and reassures that media records and backups are preserved. It also discloses the 400 refusal without confirm. The bracketed '[cvrt]' token reads like an unresolved template placeholder and slightly muddies what exactly survives.

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?

Compact and front-loaded: the destructive nature and irreversibility come before the preconditions and the confirm requirement. The stray '[cvrt]' fragment is the one piece of noise that does not earn its place.

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 two-parameter destructive tool with no annotations and no output schema, the description covers safety, preconditions, refusal codes, and what data survives. What remains unstated is the scale of deletion and whether any authentication or capability is required, both minor gaps here.

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 coverage is 100%, so both parameters are already documented in the schema, including the confirm-must-be-true behavior and the 400 refusal. The description repeats that confirm rule but adds nothing about the site parameter beyond the schema's own pointer to list_sites. 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 and resource: deleting Elementor Image Optimizer's leftover metadata and image_optimizer_* options. The precondition (migration complete) further narrows the operation, though it never names a sibling such as media_eio_dry_run or media_eio_run as the contrasting alternative.

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?

Gives a clear triggering condition (only once migration is complete) and explains that the site returns 409 while EIO is active or imports are pending, which tells the agent when not to call it. It stops short of naming an explicit alternative tool to use in those blocked cases.

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