PhotoForge MCP Server

resize_image_for_platform

Resize and crop an image to specific social media aspect ratios for Instagram, LinkedIn, TikTok, and Twitter, ensuring correctly formatted posts and banners.

Instructions

Resize and re-crop an image for specific social media aspect ratios.

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": {
      "imageUrl": "<imageUrl>",
      "platform": "<platform>"
    },
    "name": "resize_image_for_platform"
  }
}

Input Schema

Name	Required	Description	Default
`imageUrl`	Yes	Source image URL.
`platform`	Yes	Target platform aspect ratio.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 24, 2026

TDQS

B3.1/5.0

Behavior2/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 not say whether the original image is preserved or overwritten, whether the operation costs credits, whether the result is a new generation stored in the library, or what happens when the source aspect ratio already matches the target.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the behavioral and usage detail noted elsewhere rather than being a model of tight completeness.

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?

For a mutation tool with zero annotations and no output schema, the description should say what comes back (a URL, a generation ID, a library item) and whether the source is modified. None of that is covered, leaving the agent guessing about the side effects of invocation.

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%, including a fully enumerated platform list, so the schema already documents both parameters. The description adds only the framing that the platform maps to an aspect-ratio re-crop, which is helpful but not more than 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 pair ('resize and re-crop') and a specific resource ('an image') with a stated goal ('specific social media aspect ratios'). It is clearly distinguishable from siblings like export_to_social or upscale_photo, though it never explicitly names those neighbors.

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?

The purpose implies when to use it, but there is no explicit when/when-not guidance, no mention of how it relates to export_to_social (does resizing happen as part of export?), and no indication of prerequisites such as the image needing to already exist in the account.

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