Read-only MCP server that lists and diffs a Shopify store's metafield definitions, so theme work stops guessing namespaces, keys, and types.
Three read-only tools with clear, domain-specific purposes. Tool names follow verb_noun pattern (list_, get_, diff_). Descriptions are well-written (150-250 chars) and explain WHAT, WHEN, and WHY. Input schemas are present with enums for ownerType. However, critical gaps: (1) get_definition has ambiguous parameter design, accepts EITHER 'handle' OR 'namespace+key', but schema doesn't enforce mutual exclusivity or mark one as required; (2) diff_definitions accepts 'before' and 'after' with NO type constraints (should specify JSON object structure); (3) NO output schemas documented anywhere, LLMs cannot predict response structure; (4) NO error handling guidance (what if definition not found? what if snapshot malformed?); (5) parameter descriptions lack format/constraint details (e.g., 'handle' format is 'namespace.key' but not stated in description).
Compare two snapshots of metafield definitions and report what was added, removed, or changed (type, description, validations). Use this for migration planning: snapshot a source store and a target store, then diff them before moving a theme. Snapshots are JSON: either an array of definitions or a raw Admin API response ({ data: { metafieldDefinitions: { nodes: [...] } } }). Read-only.
Resolve one metafield definition by "namespace.key" (e.g. "custom.specs") to its full shape: type, description, validations, and owner type. Use this to confirm the exact namespace, key, and data type before writing Liquid. Read-only.
List all metafield definitions for an owner type (e.g. PRODUCT, COLLECTION, CUSTOMER). Returns namespace, key, type, name, and description for each, so theme work can reference real definitions instead of guessing namespaces and keys. Read-only.
Output schemas not documented. LLMs cannot predict response structure (fields, types, nesting). Rubric baseline: 100% of A+ tools document return types.
get_definition has ambiguous parameter design: accepts 'handle' OR ('namespace' + 'key'), but schema does not enforce mutual exclusivity or clarify which combination is required. LLMs will guess and pass invalid combinations.
diff_definitions 'before' and 'after' parameters have no type constraints. Schema should specify: 'object with properties: array of definitions OR { data: { metafieldDefinitions: { nodes: [...] } } }'. Current description is prose; LLMs cannot validate input format.
No error handling guidance. What happens if ownerType is invalid? If definition not found? If snapshot is malformed? Rubric requires: 'Error responses must tell the LLM what to do next.' Currently missing recovery paths.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2025-06-18+ | v2 |
Parameter descriptions lack format/constraint details. E.g., 'handle' description says 'Shorthand "namespace.key", e.g. "custom.specs"' but does not state: required format, allowed characters, length limits, or case sensitivity. Rubric: 'When a parameter has a regex pattern, length limit, or character restriction, state it in the description.'