Skip to main content
Glama

media_update_settings

Update WordPress media optimization settings such as compression, output formats, SVG uploads, and metadata handling; omitted values stay unchanged and invalid inputs are rejected.

Instructions

Update [cvrt] Media settings; omitted keys keep their value, and nothing is stored when any value is invalid. github_token is write-only: it is never returned, and a blank value keeps the stored token. To remove the token pass clear_github_token: true explicitly.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
levelNoCompression level
svg_rolesNoRoles allowed to upload SVG
avif_speedNoAVIF encoder speed, 0 (slow, smaller) to 10 (fast)
svg_enabledNoAllow safe SVG upload
webp_methodNoWebP encoder method, 0 (fast) to 6 (slow, smaller)
github_tokenNoGitHub token for plugin updates. Write-only; blank keeps the stored token
quality_avifNoAVIF quality, 1..100
quality_jpegNoJPEG quality, 1..100
quality_webpNoWebP quality, 1..100
max_dimensionNoLongest side in px; 0 disables resizing, otherwise 320..10000
output_formatNowebp_avif (WebP main, AVIF extra), webp, or keep (original format)
keep_copyrightNoKeep the copyright field when stripping metadata
strip_metadataNoRemove EXIF and other metadata
clear_github_tokenNotrue removes the stored GitHub token
optimize_on_uploadNoOptimize new uploads in the background queue
backup_retention_daysNoDays to keep backups of originals before automatic cleanup, 0..3650
remove_data_on_uninstallNoDelete plugin data when the plugin is deleted

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?

With no annotations present, the description carries the full behavioral burden, and it does well on the hardest parts: omitted keys preserve values, the write is all-or-nothing ("nothing is stored when any value is invalid"), and github_token is write-only with clear_github_token as the only removal path. It says nothing about required permissions, whether changes retroactively affect already-uploaded media, or what a successful call returns.

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?

Two tight sentences that lead with the mutation and patch semantics, then the security-sensitive token rules. No filler, though the opaque "[cvrt]" token costs a little clarity.

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 an 18-parameter mutation tool with no annotations and no output schema, the description covers the highest-risk semantics (atomicity, token write-only behavior, partial-update rule) that an agent could otherwise get wrong. Remaining gaps, such as permission requirements and whether settings apply to existing media, are secondary but not trivial for a tool that controls destructive metadata stripping and backup retention.

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%, so the schema already documents all 18 parameters, including the write-only and blank-keeps-token notes on github_token. The description's only genuinely additive parameter meaning is the omitted-keys-keep-value rule, which the schema does not state; the token details largely restate the schema text.

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 opens with a specific verb and resource ("Update [cvrt] Media settings"), which is clearly distinct from the sibling reader media_get_settings. The bracketed "[cvrt]" token is unexplained and slightly muddies the scope, but the intent is unambiguous.

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 explicit when-to-use guidance: nothing says to read current values with media_get_settings first, nor how this differs from media_bulk_action or mcp_update_media. The patch-semantics sentence implies usage (send only the keys you want changed) but never states it as a rule or names an alternative.

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