Skip to main content
Glama

create_discount

Create discount codes with percentage or fixed amount, set expiration and max redemptions to control usage.

Instructions

Create a discount code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesDiscount code (e.g., SUMMER50)
typeYesDiscount type
valueYesDiscount value (percentage: 0-100, fixed: amount in cents)
currencyNoCurrency for fixed discounts (default: EUR)
max_redemptionsNoMaximum number of times code can be used
expires_atNoExpiration date (ISO 8601 format)
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as side effects, idempotency, or error conditions (e.g., duplicate code).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (one sentence) but lacks structure that adds value. It is minimally adequate.

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?

With 6 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return values or business context (e.g., that a discount code is created and can be used later).

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 covers 100% of parameters, so baseline is 3. The description adds no additional meaning beyond what is already in the schema.

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 'Create a discount code' clearly states the verb and resource, distinguishing it from sibling tools like get_discount (read) and delete_discount (delete).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like create_checkout or when not to use it. The description lacks any usage context.

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/Selenium39/mcp-server-creem'

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