twelvebit Analytics

Save Shopify customer-type tag mappings

update_sales_config

DestructiveIdempotent

Save the complete Shopify customer-type configuration. Read get_sales_config first and preserve settings the user did not ask to change. config requires enabled, wholesale_tags, distributor_tags, d2c_tags and untagged. Each tag list replaces that type's mappings; [] clears it. Tags match exactly, ignoring case, with up to 30 tags per type and 100 characters per tag. The same tag cannot map to multiple types. untagged is unknown or d2c, and also applies to customers with tags that match no mapping; choose d2c only when the user asks for that fallback. Set enabled: true to turn classification on (requires Shopify read_customers permission). Needs write:config and an owner or member role. Changes affect future sales; existing classified orders keep their type. Does not edit tags in Shopify or import past orders.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "config": "<config>"
    },
    "name": "update_sales_config"
  }
}

Input Schema

Name	Required	Description	Default
`site`	No	Site domain (example.com), id or public id (tb_…). Optional with a site key, or when the account has one site.
`config`	Yes	Complete customer-type configuration from get_sales_config, with the requested changes applied.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A5/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: each tag list replaces that type's mappings, [] clears it, changes affect future sales, existing classified orders keep their type, and the tool does not edit Shopify tags or import past orders. This is consistent with destructiveHint=true and idempotentHint=true.

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 description is dense and front-loaded with the save action and prerequisite read step. Every sentence carries operational value, including replacement behavior, matching rules, permissions, and side effects.

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?

For a destructive nested-config mutation with no output schema, the description covers prerequisites, permissions, replacement semantics, matching constraints, fallback behavior, and side effects. An agent has enough information to invoke it correctly.

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?

Schema coverage is already 100%, but the description adds important semantics: config must be complete, each tag list replaces rather than merges, [] clears mappings, tags are case-insensitive exact matches, the same tag cannot map to multiple types, and untagged controls unknown/d2c fallback behavior.

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 uses a specific verb and resource: saving the complete Shopify customer-type tag configuration. It clearly distinguishes the write operation from the sibling read tool by instructing the agent to call get_sales_config first.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit workflow guidance: read get_sales_config first and preserve settings the user did not ask to change. It also specifies when to choose d2c for the untagged fallback and what the tool does not do.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All twelvebit Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?