Skip to main content
Glama

media_get_status

Retrieve WordPress media configuration status, including plugin version, WebP/AVIF encoders, entitlement, Elementor Image Optimizer state, and missing configured output formats for a site.

Instructions

[cvrt] Media status: plugin version, available encoders (WebP/AVIF), entitlement, Elementor Image Optimizer state, and which configured output formats are missing on this server.

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_get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does a decent job disclosing the returned content set (version, encoders, entitlement, optimizer state, missing formats), which implies a read-only probe, but it never states that it is non-mutating, whether server-side encoder probing is expensive or slow, or what happens for an unentitled site.

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?

One dense, front-loaded sentence with no padding; every clause names a concrete reported item. The only friction is the unexplained '[cvrt]' tag, which occupies the highest-attention position without adding meaning for an agent.

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 correctly compensates by enumerating the fields returned, which is the right call. However, for a diagnostic tool whose value depends on interpreting 'missing formats' and entitlement state, it omits any hint about error cases or how to act on the results.

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% and the single 'site' parameter already documents 'Site id (see list_sites)'. The description adds nothing about the site parameter, so per the high-coverage baseline a 3 is correct — the schema does the work here.

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 names a specific resource (media status) and enumerates exactly what it reports: plugin version, available encoders (WebP/AVIF), entitlement, Elementor Image Optimizer state, and missing configured output formats. That enumeration distinguishes it from a plain stats tool like media_get_stats, though the opaque '[cvrt]' prefix and the noun-phrase phrasing (no verb) slightly weaken the opening.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says to call this before attempting optimization, before media_optimize_attachment, or when diagnosing failed conversions. No alternatives are named and no exclusions are given, so the agent must infer from the sibling list that this is the diagnostic counterpart to media_get_stats.

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