Skip to main content
Glama

Crop a site image

crop_image

Crop an uploaded site image to an upright pixel rectangle. Creates a new image without modifying the source: JPEG stays JPEG, WebP and AVIF become WebP, PNG and still GIF become PNG; the result is scaled down to fit 2048 px. Unreferenced originals may be removed by normal publish cleanup. Does not alter the draft: read get_site and assign the returned URL with update_site. Inspect the photo before choosing coordinates. Animated files are rejected.

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": {
      "siteId": "<siteId>",
      "imageUrl": "<imageUrl>",
      "crop": "<crop>"
    },
    "name": "crop_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
cropYesPixel rectangle in the upright image, after EXIF orientation. This operation does not modify the original; normal unused-media cleanup still applies.
siteIdYes
imageUrlYesExact image URL uploaded to this site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses behavior an agent could not otherwise predict: format conversion rules (JPEG stays JPEG, WebP/AVIF become WebP, PNG and still GIF become PNG), downscaling to 2048 px, that the source is untouched, and that unreferenced originals may be removed by normal publish cleanup. This is consistent with destructiveHint=false and non-idempotent semantics (each call produces a new image).

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?

It is front-loaded with the core action and packed with high-value clauses (format rules, scaling, draft workflow, rejection case). The middle format-conversion sentence is dense but each clause carries distinct information; no filler is present.

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 3-parameter mutation with no output schema, the description covers side effects, format normalization, lossy size limits, cleanup risk, and the follow-up workflow. The only gap is the exact shape of the returned value, though it implies a URL exists to assign via update_site.

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 67% and the crop sub-object already documents the pixel rectangle and EXIF orientation, so the schema carries most of the load. The description reinforces that coordinates are pixels in the upright image and adds the practical caveat to inspect the photo first, but adds nothing about siteId or imageUrl beyond the schema.

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 leads with a specific verb and resource ('Crop an uploaded site image to an upright pixel rectangle') and immediately clarifies the output artifact ('Creates a new image without modifying the source'). It further separates itself from siblings by naming get_site and update_site as the drafting path, so an agent can distinguish this from upload or site-editing tools.

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?

It gives concrete preconditions and sequencing: inspect the photo before choosing coordinates, and after cropping read get_site then assign the returned URL with update_site. It also states an exclusion ('Animated files are rejected'). It stops short of naming an alternative tool for cases where cropping is inappropriate (e.g. list_images/prepare_image_upload), so it is strong but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources