Skip to main content
Glama

create_offer

Create a discount offer for a tier by specifying name, code, tier, discount type and amount, cadence, and optional duration and display information.

Instructions

Create a discount offer against a tier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesShortcode for the offer URL (yoursite.com/<code>).
nameYesInternal name (must be unique).
typeYes``percent`` or ``fixed`` — whether ``amount`` is a percentage or a fixed value.
amountYesThe discount, in percent or the smallest currency unit per ``type``.
cadenceYes``month`` or ``year`` — which of the tier's prices the offer applies to.
tier_idYesThe tier the offer applies to (from ``list_tiers``).
currencyNoRequired when ``type="fixed"``; must match the tier's currency.
durationNo``once``, ``forever``, or ``repeating`` (``repeating`` needs ``cadence="month"``).once
display_titleNoTitle shown in the offer window.
duration_in_monthsNoMonths to repeat when ``duration="repeating"``.
display_descriptionNoText shown in the offer window.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description must carry behavioral disclosure, but it only states the basic action. No details on side effects, auth needs, or constraints like unique name.

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

Conciseness4/5

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

A single, front-loaded sentence with no wasted words. However, given the tool's complexity, a bit more detail would be justified without harming conciseness.

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 a detailed schema and output schema, the description omits context like validation rules (unique name), behavior on duplicate, or relationship to list_tiers, making it incomplete for complex usage.

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 parameters are fully documented in the schema. The description adds no extra semantic value beyond what is already there.

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 offer against a tier' uses a specific verb and resource, clearly distinguishing it from siblings like update_offer or list_offers.

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 is provided on when to use this tool versus alternatives, such as update_offer, or any prerequisites like having a tier first.

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/stemcreations/ghost-mcp'

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