Skip to main content
Glama

shopify_get_theme

Read-onlyIdempotent

Retrieve a Shopify theme's details and checksum to validate approval-bound mutations. Returns id, name, role, processing state, and preimage hash for race-safe writes.

Instructions

Fetch a single Online Store theme (id, name, role, processing state) and its canonical preimage_sha256 for approval-bound mutation race checks. For an accepted non-MAIN artifact, Spring may return an opaque, expiring preview_ref bound to the exact store, theme, project, run, and artifact digest. Clients must never construct a preview URL or nominate a host/account.

Args:
    theme_id (required): Theme ID (numeric or GID).
    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
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

B3.3/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive behavior, and the description adds concrete behavioral detail: it returns a canonical preimage_sha256, may return an expiring preview_ref, and warns clients not to construct preview URLs. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with the core action front-loaded, but the second and third sentences are dense and jargon-heavy ('canonical preimage_sha256', 'approval-bound mutation race checks', 'accepted non-MAIN artifact'), reducing clarity while keeping length short.

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?

The description lacks parameter meanings, failure/error context, and any explanation of the output schema; it mentions preview_ref behavior but not enough for an agent to confidently call the tool across edge cases.

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

Parameters2/5

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

The schema has zero parameter descriptions, and the description only indirectly clarifies theme_id; project_id, project_ref, approval_ref, idempotency_key, and connector_account_ref are left unexplained. The self-explanatory names and required effect const provide minimal compensation.

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 'Fetch' and resource 'single Online Store theme' with fields, distinguishing it from sibling tools like shopify_list_themes and shopify_get_theme_files. The core purpose is immediately clear despite the extra preview_ref context.

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 explicit guidance on when to use this tool versus alternatives; it does not mention list_themes for enumeration or get_theme_files for file retrieval. The conditional preview_ref sentence reads as behavior, not usage direction.

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