Skip to main content
Glama

resize_image

Scale images to exact width and height, create thumbnails, or fit pictures within size constraints without AI processing.

Instructions

Resize images to specific dimensions without AI processing.

Use this when:

  • Scaling images to specific width/height

  • Creating thumbnails or previews

  • Fitting images within size constraints

  • Batch resizing for web optimization

NOT for:

  • AI-powered image generation (use generate_image instead)

  • Content modification with AI (use edit_image instead)

  • Format conversion only (use convert_image instead)

Example: "resize_image inputPath='./photo.jpg' width=800 height=600 fit='cover'"

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": {
      "inputPath": "<inputPath>",
      "withoutEnlargement": "<withoutEnlargement>",
      "withoutReduction": "<withoutReduction>",
      "stripMetadata": "<stripMetadata>"
    },
    "name": "resize_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNo
widthNo
heightNo
qualityNo
fileNameNo
inputPathYes
backgroundNo
outputFormatNo
stripMetadataYes
withoutReductionYes
compressionPresetNo
withoutEnlargementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses that processing is non-AI/deterministic, which is genuinely useful, but says nothing about where output is written, whether the source file is overwritten, how fileName interacts with inputPath, or the effect of stripMetadata/withoutEnlargement defaults. Calling this a 'batch' tool also conflicts with the single required inputPath parameter.

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?

Front-loaded one-liner followed by scannable use/don't-use lists and a concrete invocation example. Slight redundancy between the example and the bullet list, but every block conveys distinct routing or calling information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 12-parameter mutation tool with no annotations and no output schema needs more than this. Missing output destination, overwrite behavior, resolution of conflicting flags, and the required-parameter defaults (stripMetadata, withoutEnlargement, withoutReduction) leave an agent unable to predict the result of a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, and the description illuminates only four of them via the example (inputPath, width, height, fit). The semantics of withoutEnlargement, withoutReduction, stripMetadata, quality, compressionPreset, outputFormat, background, and fileName — including the fact that background is effectively required for fit='cover' — are left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (resize images) with an explicit scope qualifier: deterministic resizing without AI processing. The NOT-for list names the exact sibling tools that perform the confusable operations (generate_image, edit_image, convert_image), so an agent can discriminate without reading any schema.

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

Usage Guidelines5/5

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

Provides both positive triggers (thumbnails, size constraints, batch web optimization) and explicit exclusions routed to named alternatives. This is the strongest possible form of when-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.