Skip to main content
Glama

MarketPrint: Print On Demand

Upload a design image

upload_image

Upload one design image and get back an image id to use in create_shop_product. If the image is already in the account, or only on the merchant's computer, use list_my_images instead. Otherwise prefer url - the server downloads the image itself, which is fast and costs you nothing. Only fall back to imageBase64 (plus filename) for very small images, because that requires you to write out the whole encoded file and will stall on anything sizeable. Upload the artwork at its natural size - placement and scaling are decided later, per print area, in create_shop_product.

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": "upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoSTRONGLY PREFERRED. Public http(s) URL of the image - the server downloads it directly, so nothing large passes through this conversation. Use this whenever the image is reachable by URL. Provide either url or imageBase64, never both.
filenameNoFilename including the real extension, e.g. logo.png or logo.svg. Required when using imageBase64, because the extension determines how the file is processed.
imageBase64NoLAST RESORT, and only for images under roughly 100KB. You must write out the entire base64 string yourself, so a 1MB image costs hundreds of thousands of output tokens and will usually stall or be truncated before it completes. If the image is only on the merchant's computer, ask them to upload it under My Designs in the seller app and find it with list_my_images instead. Provide either url or imageBase64, never both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare it is a non-idempotent write; the description adds substantial context beyond that: the server downloads from a URL so nothing large passes through the conversation, base64 stalls/truncates on sizeable files, and placement/scaling is deferred to create_shop_product. That is exactly the kind of cost and side-effect guidance annotations cannot convey.

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 purpose and return value, then alternatives, then parameter preference, then a short caviat on sizing. Sentences are dense and purposeful; the natural-size note sits slightly apart but still earns its place.

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 3-param upload with no output schema, the description covers purpose, return value (image id), downstream consumer, permission/size constraints, and alternative tool. Nothing an agent needs to call it correctly is missing.

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% and already flags url as STRONGLY PREFERRED and imageBase64 as LAST RESORT, so much is repetition. The description still adds the filename↔base64 coupling rationale and the natural-size guidance, which goes beyond the schema's field text.

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?

States a specific verb+resource ('upload one design image') and immediately says what it returns (an image id for create_shop_product). It also names the sibling it is not (list_my_images), so an agent can distinguish it without opening a schema.

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?

Explicit when-to-use, when-not-to-use (image already in account, or only on the merchant's computer → list_my_images), and an ordered alternative preference (url first, imageBase64 as last resort). No inference required.

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