printful-mcp-server

uploadFileFromUrl

Upload an image to Printful's library directly from a public URL, making it available for product creation and mockups.

Instructions

Add a file to Printful library from a URL

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": {
      "url": "<url>"
    },
    "name": "uploadFileFromUrl"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public URL of the image file
`filename`	No	Optional filename for the file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It does not disclose whether the fetch is server-side, whether the operation is synchronous, what constraints exist on the URL or file size, authentication requirements, or what the return value indicates. 'Add a file' is too opaque.

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?

The description is a single sentence with a clear verb and object, front-loaded with the action and resource. It contains no wasted words and is appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool, the description states the core purpose and source, and the schema covers both parameters fully. However, the absence of any behavioral context, return semantics, or usage guidance leaves gaps that matter in practice, making it minimally viable but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents both parameters with 100% coverage, so the description adds little beyond restating the URL source. The 'from a URL' phrase aligns with the 'url' parameter but provides no extra semantic depth, so the baseline of 3 is appropriate.

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 uses a specific verb ('Add') and names the resource ('file to Printful library') with the source method ('from a URL'). It is clear and largely self-contained, but it does not explicitly differentiate from the sibling tool 'uploadFile', relying instead on the URL source to imply the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not say when to prefer this tool over 'uploadFile' or any other file-related sibling, nor does it mention prerequisites, exclusions, or alternative tools.

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