Skip to main content
Glama

Smart Resize

adgpt_image_resize
Destructive

Smart Resize: subject-preserving platform-size renditions of your generated image ads — presets catalog, asset context, async batch (25 credits per size), batch status, and a campaign's existing renditions. Actions: smartPresets, smartResize, smartBatchStatus, smartAssetContext, smartCampaignRenditions. Call adgpt_capabilities with the operationId to see an action's parameters.

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": {
      "action": "<action>"
    },
    "name": "adgpt_image_resize"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoParameters for the action (see adgpt_capabilities).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The description adds real value beyond the annotations by disclosing the cost model ('25 credits per size') and that batching is async, plus the subject-preserving behavior of the resize itself. It does not explain the destructiveHint=true implication — whether resizing overwrites or replaces existing assets — which is the single most important behavioral fact for this mutation tool, and it does not describe what batch status returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence front-loads the value proposition well, but the explicit action enumeration duplicates the schema enum word-for-word, spending words on information the agent already has. The trailing pointer sentence is useful; the action list is not.

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 dispatcher tool with a free-form params bag and no output schema, the definition does the essential job: it names the actions, states the credit cost, flags asynchrony, and routes the agent to adgpt_capabilities for per-action parameters. What is missing is the destructive/overwrite semantics and any indication of which actions are reads vs. writes, which matters because the single destructiveHint applies to the whole tool.

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 coverage is only 50% and the only semi-documented parameter is the free-form 'params' object, whose properties are entirely hidden behind 'see adgpt_capabilities'. The description repeats the action enum verbatim rather than explaining what any action's params require, so it fails to compensate for the low coverage and effectively forces a second lookup call with no guidance on what to look for per action.

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?

The description gives a concrete verb+resource ('subject-preserving platform-size renditions of your generated image ads') and enumerates the five distinct capabilities served by this dispatcher. It is clear what the tool does, though as a multi-action bundle the purpose is somewhat diffuse and it never names a sibling tool it differs from (e.g. adgpt_edit_creative or adgpt_single_asset).

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?

Usage is implied by the action list — presets catalog, asset context, batch resize, batch status, campaign renditions — so an agent can infer which action fits which situation. However, there is no explicit when-to-use vs. when-to-use-an-alternative guidance, and it never distinguishes this tool from the many sibling creative/asset tools.

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