Skip to main content
Glama

shopify_list_files

Read-onlyIdempotent

List Shopify files to find and reuse existing store imagery instead of re-uploading. Supports search, pagination, and returns file status, URL, and dimensions.

Instructions

List shop files ([{id, status, url, alt, width, height, created_at}]). Use it to reuse imagery the store already owns instead of re-uploading.

Args:
    limit: Maximum files to return (1-250).
    query: Optional Shopify search query (e.g. 'filename:hero*').
    after: Pagination cursor from a previous call's next_cursor.
    project_id: Authenticated Project UUID.
    project_ref: Exact project correlation reference.
    connector_account_ref: Project-bound connector account alias.
    idempotency_key: Stable business-action identity.
    effect: Required and must be read; Spring verifies it.
    approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
limitNo
queryNo
effectYes
project_idNo
project_refNo
approval_refNo
idempotency_keyNo
connector_account_refNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior; the description does not contradict them. It adds meaningful context about output shape and pagination via the `after` cursor and the limit constraint.

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?

Front-loaded one-line summary and use case, followed by a compact Args block. No fluff, though 'Spring verifies it' and some generic parameter glosses add little.

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

Completeness4/5

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

For a 9-parameter tool, the description covers purpose, use case, pagination, search syntax, and parameter roles, and an output schema exists so return details are not its job. It could be improved by clarifying defaults and the optional platform metadata fields, but it is sufficient for correct invocation.

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 description coverage is 0%, so the description carries the burden; it defines all 9 parameters. Core parameters get real semantics: limit range (1-250), query syntax with example, after as pagination cursor from next_cursor, and effect must equal read. Platform params are still terse boilerplate, so not perfect.

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 verb and resource ('List shop files') and includes the return field shape, which anchors what the tool does. The reuse-imagery line further frames it as the read/reuse counterpart to upload tools. Clear enough to tell apart from sibling theme-file tools.

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

Usage Guidelines4/5

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

Explicitly prescribes the use case: 'reuse imagery the store already owns instead of re-uploading,' which tells an agent when to choose this tool. It does not name alternatives or state when not to use it, but the context is unambiguous.

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/RPasquale/lightbulb-mcp'

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