Skip to main content
Glama
untitled-developers

Kockatoos Shopify MCP Server

create_code_discount_basic

Create a percentage or fixed amount discount code for customers at checkout. Target specific products or collections, set minimum subtotal or quantity, and define combination rules.

Instructions

Create an amount-off code discount (percentage or fixed) that customers apply at checkout. Supports product/collection targeting, minimum requirements, and combination rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesInternal name shown in admin.
codeYesCode customers enter at checkout (e.g. 'SAVE10').
startsAtYesActivation date (ISO 8601).
endsAtNoExpiry date (ISO 8601).
usageLimitNoMax total redemptions. Omit for unlimited.
appliesOncePerCustomerNoLimit one use per customer. Default: false.
discountTypeYesType of discount.
discountValueYesPercentage (0–100, e.g. 10 for 10%) or fixed dollar amount (e.g. 10).
appliesOnEachItemNoFor fixed_amount: apply to each eligible item. Default: false.
appliesToAllNoApply to all products. Default: true.
productIdsNoGIDs of products to target (e.g. 'gid://shopify/Product/123').
collectionIdsNoGIDs of collections to target.
variantIdsNoGIDs of product variants to target.
minimumSubtotalNoMinimum order subtotal required (e.g. 50 for $50).
minimumQuantityNoMinimum quantity of items required.
combinesWithNoDiscount classes this discount can combine with.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool creates discounts with targeting, minimum requirements, and combination rules, but does not discuss side effects, permissions, or limits like daily usage caps or discount code uniqueness.

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?

Two sentences concisely capture the tool's purpose and core features with no redundancy. Information is front-loaded and each sentence adds value.

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?

Given 16 parameters and no output schema, the description provides a sufficient high-level overview. It covers the main capabilities but does not explain return values or error conditions, which is acceptable for a creation tool with rich schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no extra detail beyond summarizing the overall purpose; it doesn't clarify edge cases or provide examples for complex fields like 'combinesWith'.

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 explicitly states it creates an amount-off code discount (percentage or fixed), distinguishes from sibling tools like bxgy and free shipping, and specifies key features like targeting and combination rules.

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 implies usage for amount-off discounts, differentiating it from bxgy and free shipping siblings, but does not explicitly state when to use this tool vs alternatives or provide any exclusion criteria.

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/untitled-developers/shopify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server