Skip to main content
Glama

media_reoptimize_attachment

Re-optimizes a single media attachment from its backed-up original using current settings, so you can refresh one item after configuration changes.

Instructions

Re-optimize one attachment from its backed-up original with the current settings.

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

Input Schema

NameRequiredDescriptionDefault
idYesAttachment id
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/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 burden. It usefully discloses the mechanism — output is re-derived from the backup original rather than recompressed in place — but says nothing about side effects (whether the current file/thumbnails are replaced), whether backups are consumed, permissions, or synchronous vs queued execution.

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?

A single well-formed sentence with the resource and the operation's source-of-truth front-loaded. No filler, no redundancy.

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?

A mutation tool with no annotations and no output schema needs more than one sentence: the backup prerequisite, failure mode without a backup, and whether the result replaces the live attachment are all missing. The core mechanism is conveyed adequately, but an agent could call this on an attachment that has never been backed up without warning.

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% for both parameters; the schema already documents id and site (with a pointer to list_sites). The description adds no extra semantics for either parameter, so the 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?

Specific verb+resource: re-optimize a single attachment, and the description adds the distinguishing mechanism — it regenerates from the backed-up original using current settings, which separates it from a plain optimize call on the live file. It does not name media_optimize_attachment or media_restore_attachment explicitly, so sibling differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'from its backed-up original with the current settings' — presumably re-run after a settings change — but the description never says when to pick this over media_optimize_attachment or media_restore_attachment. The key prerequisite (an existing backup) and the behavior when no backup exists are unstated.

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