Delete specific metafields from any Shopify resource by specifying owner ID, namespace, and key to clean up or remove unwanted data.
Delete metafields from any Shopify resource by specifying owner ID, namespace, and key.
| Name | Required | Description | Default |
|---|---|---|---|
| metafields | Yes | Metafields to delete, identified by owner + namespace + key |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden for a destructive operation. It does not state that deletion is irreversible, whether the batch is atomic, what permissions/access scopes are required, or what happens if an ownerId/namespace/key combination does not exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. It is efficient, though it stops short of including any operational detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The schema is fully described and there is only one parameter, so invocation is unambiguous. However, for a destructive tool with zero annotation coverage and no output schema, the absence of irreversibility and error-handling context leaves a material gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so types and the ownerId GID format are already documented in the schema. The description restates the addressing triple but adds no batching semantics or error behavior beyond what the schema says.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (delete) and resource (metafields) plus the identifying triple (owner ID, namespace, key), and clarifies scope with 'any Shopify resource'. It is distinguishable from get-metafields and set-metafields by verb alone, though siblings are never named.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus set-metafields or when a metafield should not be removed. The existence of the sibling set_metafields/get_metafields family is left for the agent to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.