Skip to main content
Glama
untitled-developers

Kockatoos Shopify MCP Server

create_price_rule

Create a basic code discount in Shopify using GraphQL. Define discount type, value, eligibility, and duration.

Instructions

Create a modern basic code discount through GraphQL. Preserves the legacy price-rule tool name for compatibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPrice rule title (internal name).
target_typeYesWhat the discount applies to.
target_selectionYesWhich items the discount targets.
allocation_methodYesHow the discount is allocated: 'across' splits evenly, 'each' applies to each item.
value_typeYesType of discount value.
valueYesDiscount value (negative number, e.g. '-10.0' for 10% or $10 off).
customer_selectionNoWhich customers qualify. Default: all.all
starts_atYesWhen the discount becomes active (ISO 8601).
ends_atNoWhen the discount expires (ISO 8601).
usage_limitNoMaximum total number of times the discount can be used.
once_per_customerNoLimit to one use per customer. Default: false.
Behavior2/5

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

No annotations provided; description only states it creates a discount. Does not disclose mutation, side effects, permissions, or whether it is destructive. Minimal behavioral context.

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, no redundancy. Front-loads purpose, then explains naming. All sentences are necessary and clear.

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?

Despite 11 parameters and no output schema, the description is very brief. Does not explain workflow, required negative value, or relation to discount codes. Incomplete for agent decision-making.

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 baseline 3. Description adds no parameter-level beyond the schema; no examples or interaction hints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it creates a modern basic code discount via GraphQL. It clarifies legacy naming but does not explicitly differentiate from sibling tools like create_code_discount_basic.

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

Usage Guidelines3/5

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

Implies this is for legacy price-rule compatible discounts, but no explicit guidance on when to use this vs create_code_discount_basic or other discount tools. Lacks when-not or alternative references.

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