Skip to main content
Glama

Print Shop by Bottle Your Brand

Upload sticker artwork

upload_sticker_artwork

Show an upload panel in the conversation for custom die-cut sticker artwork that has no public image URL. If the image is in this conversation — uploaded by the customer or generated by you — pass it as artwork: the panel then opens with it already loaded and an "Order these stickers" button that opens the Bottle Your Brand order page with the artwork attached. Without artwork the panel shows a drop zone for a file on their device. Prefer order_custom_stickers when a public https image URL is available.

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_sticker_artwork"
  }
}

Input Schema

NameRequiredDescriptionDefault
artworkNoThe image from this conversation the customer wants printed: one they uploaded or one you generated. Pass it whenever such an image exists, so the panel opens with it already loaded. Leave it out only when there is no image in the conversation.

Output Schema

NameRequiredDescriptionDefault
readyNoPre-loaded artwork; when present the panel shows it ready to order.
productYesProduct key the upload panel orders for.
load_errorNoWhy a chat image could not be loaded; the panel shows it.
uploadBaseYesOrigin the panel uploads to.
upload_urlYesPage to use if the panel cannot be shown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / artwork / description
      Previous value: -"Set by the upload panel itself. Never fill this in."New value: +"The image from this conversation the customer wants printed: one they uploaded or one you generated. Pass it whenever such an image exists, so the panel opens with it already loaded. Leave it out only when there is no image in the conversation."
    • addedOutput schema / properties / load_error
      Added value: +{
      +  "description": "Why a chat image could not be loaded; the panel shows it.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / artwork
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Set by the upload panel itself. Never fill this in.",
      +  "properties": {
      +    "download_url": {
      +      "type": "string"
      +    },
      +    "file_id": {
      +      "type": "string"
      +    },
      +    "file_name": {
      +      "type": "string"
      +    },
      +    "mime_type": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "file_id",
      +    "download_url"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / ready
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Pre-loaded artwork; when present the panel shows it ready to order.",
      +  "properties": {
      +    "file": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "expiresAt": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "previewUrl": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "type": {
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "type",
      +        "url",
      +        "previewUrl",
      +        "expiresAt"
      +      ],
      +      "type": "object"
      +    },
      +    "handoffUrl": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "file",
      +    "handoffUrl"
      +  ],
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / artwork
      Removed value: -{
      -  "additionalProperties": {},
      -  "description": "A file the host attached from the conversation (uploaded or AI-generated). Set automatically by the host — never fabricate it. Leave unset when there is no such file.",
      -  "properties": {
      -    "download_url": {
      -      "type": "string"
      -    },
      -    "file_id": {
      -      "type": "string"
      -    },
      -    "file_name": {
      -      "type": "string"
      -    },
      -    "mime_type": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "file_id",
      -    "download_url"
      -  ],
      -  "type": "object"
      -}
    • removedOutput schema / properties / ready
      Removed value: -{
      -  "additionalProperties": false,
      -  "description": "Pre-loaded artwork; when present the panel shows it ready to order.",
      -  "properties": {
      -    "file": {
      -      "additionalProperties": false,
      -      "properties": {
      -        "expiresAt": {
      -          "type": "string"
      -        },
      -        "name": {
      -          "type": "string"
      -        },
      -        "previewUrl": {
      -          "type": [
      -            "string",
      -            "null"
      -          ]
      -        },
      -        "type": {
      -          "type": "string"
      -        },
      -        "url": {
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "name",
      -        "type",
      -        "url",
      -        "previewUrl",
      -        "expiresAt"
      -      ],
      -      "type": "object"
      -    },
      -    "handoffUrl": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "file",
      -    "handoffUrl"
      -  ],
      -  "type": "object"
      -}
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare openWorldHint=true and destructiveHint=false; the description adds the concrete consequence — the panel opens pre-loaded and its 'Order these stickers' button navigates to the external Bottle Your Brand order page. That is real context beyond the annotations. It stops short of mentioning permissions or what the tool returns, so it is not exhaustive.

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?

Three sentences, front-loaded with the core purpose and ending with the alternative-tool rule. The middle sentence about the order button is slightly long but carries information an agent needs to set expectations for the user.

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?

Output schema exists, so return values need no explanation, and the single optional parameter is fully documented in both schema and description. Nothing an agent needs in order to call this correctly or route around it 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%, so the baseline is 3; the description earns more by giving a decision rule the schema cannot — pass artwork whenever an in-conversation image (customer-uploaded or agent-generated) exists, and leave it out only when there is none. That resolves the ambiguity of a single optional nested parameter.

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 action and resource — show an upload panel in the conversation for custom die-cut sticker artwork that lacks a public image URL. The scoping clause ('no public image URL') immediately separates it from the sibling order_custom_stickers without needing to open either 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?

Gives an explicit routing rule: 'Prefer order_custom_stickers when a public https image URL is available,' and separately tells the agent when to pass artwork versus omit it. Both the when-to-use and when-not-to-use cases are covered.

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