Skip to main content
Glama

shopify_get_theme_files

Read-onlyIdempotent

Fetch up to 50 Shopify theme files by exact filename to read current code before editing, ensuring updates preserve the theme structure.

Instructions

Fetch the bodies of up to 50 theme files by exact filename. Read files before editing them so upserts preserve the base theme's structure.

Args:
    theme_id (required): Theme ID (numeric or GID).
    filenames (required): Exact filenames to fetch (1-50 per call).
    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
effectYes
theme_idNo
filenamesNo
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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description does not contradict them. It adds value beyond those annotations by disclosing the 50-file cap, the exact-filename requirement, the read-before-upsert workflow intent, and the Spring-verified effect contract.

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 purpose sentence is front-loaded, the workflow guidance is one compact sentence, and the Args block is scannable with no filler. Each line earns its place by adding a type, constraint, or semantic clarification.

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?

Combined with read-only/idempotent annotations and a provided output schema, the description covers what the tool does, when to call it, how many files it accepts, and the meaning of every parameter. Nothing essential for invoking it correctly 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?

With 0% schema description coverage, the Args block compensates thoroughly by explaining theme_id as numeric or GID, filenames as exact with a 1-50 cap, and the correlation/framework parameters with one-line meanings. The main blemish is that theme_id and filenames are marked '(required)' in the text while the schema lists only effect as required, which could confuse an agent reconciling the two sources.

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 starts with a specific verb and resource: 'Fetch the bodies of up to 50 theme files by exact filename.' This clearly distinguishes it from list_theme_files (listing filenames) and upsert/delete theme file tools, so an agent can tell exactly what operation this tool performs.

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?

It gives a clear when-to-use rule: 'Read files before editing them so upserts preserve the base theme's structure.' It does not explicitly name sibling alternatives like list_theme_files for discovering filenames or state cases where the tool should not be used, so it stops short of full routing guidance.

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