Print Shop by Bottle Your Brand

Upload sticker artwork

upload_sticker_artwork

Show an upload panel in the conversation so the customer can drop in artwork that lives on their device — including a file they shared in this chat, which cannot be passed to a tool directly. Use this whenever someone wants stickers made from a file they have but no public image URL. They pick the file, see it, and get a button that opens the Bottle Your Brand order page with the artwork already attached. Prefer order_custom_stickers instead when a public https image URL is available.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`product`	Yes	Product key the upload panel orders for.
`uploadBase`	Yes	Origin the panel uploads to.
`upload_url`	Yes	Page to use if the panel cannot be shown.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

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

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description explains the actual mechanics: the file never passes through a tool, the panel is customer-driven, and the resulting button opens an external Bottle Your Brand page with the artwork attached — which justifies the openWorldHint. It also explains the key edge case (a file shared in chat cannot be passed directly), a behavioral trait no annotation conveys.

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?

Three sentences, front-loaded with the action, then the trigger condition, then the alternative. Every sentence contributes routing or behavioral information; there is no filler or restatement of the title.

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 an output schema present and no parameters, the description only needs to explain the interaction model, which it does fully: what appears, who acts, and where the user ends up. Nothing an agent needs in order to choose or invoke this tool 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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly conveys that all input comes from the interactive panel rather than from arguments.

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 description uses a specific verb and resource — 'Show an upload panel in the conversation' — and immediately states the outcome: the customer drops in a device-local file so it can be attached to an order. It also clearly names the sibling it is not (order_custom_stickers), so an agent can distinguish the two tools without inspecting 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?

It gives an explicit trigger ('whenever someone wants stickers made from a file they have but no public image URL') and an explicit exclusion plus alternative ('Prefer order_custom_stickers instead when a public https image URL is available'). Both routing conditions are stated outright, leaving nothing to inference.

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

All Print Shop by Bottle Your Brand tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?