printful-mcp-server

getFiles

Retrieve a list of all files in your Printful library. Filter by status and paginate results.

Instructions

Get list of all files in your Printful library

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

Input Schema

Name	Required	Description
`limit`	No	Number of results (max 100)
`offset`	No	Pagination offset
`status`	No	Filter by file status

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 provided, the description must disclose behavior itself. It only states 'Get list of all files' without mentioning pagination, status filtering, return format, or rate limits. The word 'all' is potentially misleading given the limit and offset parameters.

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, front-loaded sentence with the verb and resource stated directly. Every word earns its place, with no redundancy or filler.

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?

Given the simplicity of the tool (3 optional params, no output schema), the description provides the basic purpose but lacks context about pagination semantics, what 'library' refers to, or how results are returned. It is minimally sufficient but not fully self-contained without annotations.

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 provides 100% coverage for all three parameters (limit, offset, status) with descriptions. The tool description adds no extra meaning beyond the schema and does not clarify how 'all files' interacts with pagination, so it neither improves nor degrades the schema's baseline.

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 clear verb 'Get' and identifies the resource as 'files in your Printful library'. It distinguishes from getFile (singular) but does not explicitly differentiate from getPrintfiles or other list operations, leaving some ambiguity.

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 guidance is provided on when to use this tool versus alternatives like getFile, getPrintfiles, or uploadFile. There is no mention of prerequisites, typical scenarios, or exclusions.

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