Skip to main content
Glama

resize_image

Resize images by specifying dimensions or scale factor while preserving aspect ratio. Adjust width, height, or scale to modify image size for different requirements.

Instructions

Resize an image by dimensions or scale factor.

Provide width/height, or a scale factor (e.g. 0.5 for half size). By default, aspect ratio is preserved. If only width or height is given, the other dimension is calculated automatically.

Args: path: Absolute path to the image file. width: Target width in pixels. height: Target height in pixels. scale: Scale factor (e.g. 0.5 = half, 2.0 = double). keep_aspect_ratio: Preserve aspect ratio when both width and height given. output_path: Where to save. Defaults to _resized. next to input.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
widthNo
heightNo
scaleNo
keep_aspect_ratioNo
output_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries full burden and does well by explaining key behaviors: aspect ratio preservation by default, automatic dimension calculation when only one dimension is provided, and default output naming convention. It doesn't cover error conditions or performance characteristics.

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?

The description is efficiently structured with a clear purpose statement followed by detailed parameter explanations in a labeled 'Args' section. Every sentence adds value with no redundancy or unnecessary information.

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

Completeness5/5

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

Given the tool's complexity (6 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description provides complete context: clear purpose, parameter semantics, behavioral details, and usage guidance without needing to explain return values.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining all 6 parameters in detail: what each parameter does, how they interact (width/height vs. scale), default behaviors, and the output_path default naming convention.

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?

The description clearly states the tool's purpose with specific verbs ('resize an image') and resources ('image'), and distinguishes it from siblings by focusing on dimension/scale-based resizing rather than cropping, rotating, or other image operations.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool (resizing by dimensions or scale) and how parameters interact, but doesn't explicitly mention when not to use it or name specific alternatives among the sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Adityaaery20/media-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server