Skip to main content
Glama
UVU-Store

shopify-graphql-mcp

by UVU-Store

get_files

Fetch files uploaded to a Shopify store, including images, videos, and PDFs. Filter by filename or MIME type, sort, and paginate to locate specific assets.

Instructions

Fetch files uploaded to the store (images, videos, PDFs, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoCursor for pagination
firstNoNumber of files to fetch (1-250, default: 50)
queryNoFilter query (e.g., 'filename:image', 'mimeType:image/*')
reverseNoReverse the sort order
sortKeyNoField to sort by
Behavior2/5

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

There are no annotations, so the description must disclose behavioral traits. It only states the action without mentioning pagination, return format, side effects, or permissions. 'Fetch' implies read-only but no explicit safety info is given.

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 no wasted words. It directly conveys the tool's purpose and examples, fitting within the concise length standard.

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

Completeness2/5

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

Despite having 5 optional parameters, no output schema, and no annotations, the description only provides a basic action statement. It fails to mention return values, pagination behavior, filtering options, or any limitations, leaving the agent without enough context for correct invocation.

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 has 100% coverage of parameter descriptions, so the schema already explains each parameter. The description adds no information about parameters, but per the rubric baseline is 3 for high schema coverage.

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 'Fetch' with the resource 'files' and scopes it to 'uploaded to the store', clearly distinguishing it from sibling tools like get_file (singular) or get_theme_files. It also gives examples of file types, making the purpose unambiguous.

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 such as get_file or get_theme_files. The description doesn't mention any exclusions or prefer conditions, so the agent has to infer usage from the name and context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/UVU-Store/shopify-graphql-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server