Skip to main content
Glama

Resize a picture

postfjord_resize_media

Generates resized copies of a media library image in specified aspect ratios for social formats, returning new media IDs while keeping the original unchanged.

Instructions

Makes new pictures of other shapes from one picture in the media library, one new file per shape (like Magic Resize), and returns their mediaIds. The original never changes. Shapes: 1x1 (square), 4x5 (portrait feed), 9x16 (story and reel), 16x9, 1.91x1, 3x2, 2x3, 4x3; at most one of each in a call. You can call it right after postfjord_upload_media with the new id: it waits a few seconds for the picture to be ready. Each size is a shape alone ("9x16") for the automatic crop, where Postfjord picks the best part, or { aspect, mode, focus, zoom }: mode crop with focus { x, y } (0 to 1 from the top left of the original) on what must stay and zoom 1 to 4, or mode whole to show the whole picture on a soft blurred copy of itself. Use mode whole when a crop would cut off people (heads, hands, feet) or words in the picture (a poster, a menu, a quote). Check the result with postfjord_get_media (previews) before you use it. The new files count toward the plan's storage, and each plan makes a number of resized pictures a day; over it the call is refused. On a retry after a timeout or error, send the same idempotency_key: the first answer comes back and nothing is made or sent twice.

Input Schema

NameRequiredDescriptionDefault
sizesYesThe shapes to make. Common: ["1x1", "4x5", "9x16"].
mediaIdYesThe picture to resize, from postfjord_list_media or postfjord_upload_media.
idempotency_keyNoYour own id for this one action, for example post-20261006-launch. Make a new one for each new thing; send the same one again only when you retry. Left out, the exact same call within 10 minutes counts as a retry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the original is never modified, new files consume plan storage, a per-plan daily resize quota can refuse the call, and the tool briefly waits for a freshly uploaded picture to be ready. Retry semantics with idempotency_key are spelled out, which is important given idempotentHint=false.

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 with what the tool does and what it returns, then shapes, then modes, then quotas and retries — a sensible order. The middle section is a dense run-on covering mode/focus/zoom that could be tightened, but no sentence is filler.

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?

For a mutation tool with no output schema, the description covers output (mediaIds), side effects (storage and daily quota), source-state caveat (waits for upload readiness), and retry safety. An agent has everything needed to invoke it correctly and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning: at most one of each shape per call, the string form means automatic crop while the object form exposes mode/focus/zoom, and focus is defined as the point that must stay centered. It does not restate the idempotency_key field's own documented behavior, which the schema already covers.

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?

Specific verb and resource: it makes new resized copies of one media-library picture, one file per shape, and returns mediaIds. It explicitly distinguishes itself from adjacent tools (postfjord_upload_media for the source id, postfjord_get_media for verification, postfjord_make_reel by implication).

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?

Gives explicit when-to-use context: call right after postfjord_upload_media with the new id, check results with postfjord_get_media first. It also gives a concrete decision rule for mode whole (when a crop would cut off heads, hands, feet, or words) versus the automatic crop.

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