Skip to main content
Glama

shopify_delete_theme_files

DestructiveIdempotent

Delete up to 50 files from a Shopify development theme while protecting main and release-candidate themes from mutation.

Instructions

Delete up to 50 files from a DEVELOPMENT theme. This operation currently fails closed before dispatch until Spring can durably retain a complete recovery snapshot before the provider boundary. UNPUBLISHED release candidates and MAIN themes are immutable (SHOPIFY_THEME_ROLE_PROTECTED).

Args:
    theme_id (required): DEVELOPMENT theme ID (numeric or GID).
    filenames (required): Exact filenames to delete (1-50 per call).
    expected_preimage_sha256 (required): Exact governed get_theme lifecycle digest approved for deletion.
    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: Claimed read or write effect; Spring verifies it.
    approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectNo
theme_idNo
filenamesNo
project_idNo
project_refNo
approval_refNo
idempotency_keyNo
connector_account_refNo
expected_preimage_sha256No

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.4/5.0
Behavior4/5

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

Annotations already mark this destructive and non-read-only, and the description adds meaningful behavioral context: the operation fails closed until a recovery snapshot can be retained, and certain theme roles are protected. It does not contradict annotations, though it leaves some internal mechanics (e.g., Spring provider boundaries) unexplained.

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?

The main behavior and critical constraints are front-loaded in two sentences, and the parameter list is compact. The description earns its length for a destructive 9-parameter tool, though internal jargon such as Spring, provider boundary, and governed lifecycle digest adds cognitive load.

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?

The description covers safety, role immutability, idempotency, and the digest precondition, and an output schema exists, so return details are not needed. It does not explain how to obtain expected_preimage_sha256 or the approval flow, but the reference to get_theme and approval_ref provides enough orientation for an agent with sibling-tool context.

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

Parameters5/5

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

With 0% schema description coverage, the description carries the full burden for the 9 parameters, and it delivers: it marks required fields, defines accepted formats (numeric or GID), bounds filenames to 1-50, and explains the preimage digest, idempotency key, effect, and approval_ref semantics. This is substantial meaning beyond the raw schema.

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 opening sentence names a specific verb (Delete), resource (theme files), capacity (up to 50), and target scope (DEVELOPMENT theme), which distinguishes it from read/list/update theme-file tools. The immutability statement further defines exactly which theme roles this tool applies to.

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?

The description clearly tells the agent when this tool is appropriate (deleting files from DEVELOPMENT themes) and explicitly when it is not (UNPUBLISHED release candidates and MAIN themes are immutable). It does not name sibling alternatives such as shopify_upsert_theme_files or shopify_get_theme_files, so the guidance stops short of a full routing rule.

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