Skip to main content
Glama

media_svg_backfill

Adds missing width and height attributes to SVG media attachments, processing up to a set limit per call and reporting updated and remaining files.

Instructions

Write width and height into SVG attachments that have none, up to limit per call; returns { updated, remaining }.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
limitNoMost SVG attachments handled in this call, 1..500

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the key behavior: only SVGs lacking width/height are touched, work is capped per call, and progress is returned as { updated, remaining }. It does not say whether files on disk are rewritten, whether the operation is reversible, what permissions are needed, or what happens to malformed SVGs.

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 compact sentence with the core action front-loaded and the return shape appended after the semicolon. Nothing is padded and every clause conveys 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 two-parameter tool with no output schema, the description usefully spells out the return payload and the batching/continuation model. The only meaningful gap is side-effect disclosure about the underlying files, which matters for a mutation tool with no annotations.

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 'site' (with a pointer to list_sites) and 'limit' (1..500) are already fully documented in the schema. The description's 'up to limit per call' restates the parameter without adding format or selection semantics, so it sits at the baseline.

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: writing width and height attributes into SVG attachments that currently have none, capped per call. This is inherently distinct from every sibling (list/get/update/delete/optimize), though the description never names an alternative to route an agent away from.

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 rather than prescribed: 'up to limit per call' plus the returned 'remaining' value hints that the tool is intended to be called repeatedly until remaining reaches zero. There is no explicit when-to-use, when-not-to-use, or prerequisite statement (e.g., run after sideloading or migrating SVGs).

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