Skip to main content
Glama

Upload a product image

adgpt_upload_product_image

Upload a product photo to AdGPT from the local machine — pass an absolute file_path (preferred) OR data_base64 (+ filename). Validates it is a usable product image (min 100×100px, aspect between 1:4 and 4:1), stores it, and returns {url, width, height}; pass that url in user_instructions.uploaded_images when creating a campaign (up to 5). Formats: jpeg/png/webp/gif/bmp, max 10MB. Works before login too.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adgpt_upload_product_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNoFilename for data_base64 uploads (extension sets the type), e.g. product.png.
file_pathNoAbsolute path to the image on the machine running the MCP server.
data_base64NoRaw base64 image data (no data: prefix). Alternative to file_path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare write/idempotency/destructive flags; the description adds substantial context beyond them: validation thresholds (100×100px, aspect 1:4–4:1), format and 10MB limits, the 5-image cap, the exact return shape, and the non-obvious fact that it works before login. These are precisely the constraints an agent needs and none contradict the annotations.

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?

A single dense paragraph ordered as action → input choice → validation → return → downstream use → limits. Every clause carries operational information; nothing restates the title or wastes a sentence.

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?

With no output schema present, the description supplies the return shape, and it covers the input alternatives, failure conditions, and size/format limits. For a 3-parameter upload tool this leaves no material gap for an agent to guess at.

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 the baseline is 3, but the description adds real meaning: the two parameters are mutually exclusive alternatives, file_path is preferred, and filename is coupled to data_base64. That dependency and preference ordering is not expressed in the schema itself.

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 first clause pairs a specific verb and resource ('Upload a product photo to AdGPT') and immediately states the two input modes and the validated output ({url, width, height}). An agent can distinguish this from siblings like adgpt_image_resize or adgpt_single_asset without opening any schema.

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 a clear preference order (absolute file_path preferred, data_base64 + filename as fallback) and names the downstream consumer ('pass that url in user_instructions.uploaded_images when creating a campaign'), which tells the agent where this fits in a workflow. It stops short of stating when NOT to use it versus the sibling image 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