Skip to main content
Glama

gumroad

by io.usefulapi

Create offer code

gumroad_create_offer_code
Destructive

Create a new offer code (discount code) on a product. Gumroad REST: POST /v2/products/{product_id}/offer_codes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe discount code text buyers enter (e.g. LAUNCH20).
universalNoWhether the offer code applies to all of the user's products (default false).
amount_offYesThe amount off — in cents when offer_type is 'cents', or a percentage when 'percent'.
offer_typeNoWhether amount_off is a fixed amount in 'cents' or a 'percent' discount (default 'cents').
product_idYesThe product id to create the offer code on.
max_purchase_countNoOptional cap on how many times the offer code can be used.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.2/5.0
Behavior1/5

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

The description says 'Create a new offer code,' which is an additive operation, but the annotations declare destructiveHint: true. This is a direct contradiction, so per the rubric the score is 1. The description also does not disclose any behavioral details beyond the contradiction.

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 two sentences long, front-loaded with the purpose, and includes a helpful REST endpoint. Every word provides useful context with no redundancy.

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?

The description is minimal despite the tool having 6 parameters and no output schema. It does not mention the return value, potential errors, idempotency, or any side effects beyond creation. The REST endpoint adds some context but the overall guidance is incomplete.

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?

The schema provides 100% coverage with clear descriptions for all 6 parameters, including the special behavior of amount_off depending on offer_type. The description adds no parameter-specific meaning beyond what the schema already provides.

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 'Create a new offer code (discount code) on a product,' which clearly identifies the action and resource. The REST endpoint further specifies the target and distinguishes this from sibling tools like update_offer_code or list_offer_codes.

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?

The description implies this tool is for creating offer codes, but it does not explicitly state when to use it over alternatives like update_offer_code. The usage context is inferred from the verb 'Create' rather than stated.

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

All gumroad toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool targets a distinct resource (product, offer code, license, sale, subscriber, user, variant category, custom field, resource subscription) with a specific action (get, list, create, update, enable, disable, verify). Even the license tools (enable, disable, verify) are clearly differentiated by their descriptions, and no two tools overlap in purpose.

Naming Consistency5/5

All tools follow the consistent pattern of 'gumroad_' + verb (create, get, list, update, enable, disable, verify) + noun in snake_case. The verbs and nouns are uniformly chosen, making the API predictable and easy to navigate.

Tool Count3/5

20 tools is in the 16-25 range that feels heavy, but the breadth is justified by Gumroad's multiple resource types. However, the number leans toward the upper bound, and some resources have only partial CRUD coverage, so the count is borderline.

Completeness2/5

The tool set is read-heavy: products lack create/update/delete, offer codes lack delete, resource subscriptions lack create/delete, and custom fields only have list. These significant gaps prevent agents from performing full lifecycle management, which will cause failures for common workflows like publishing a new product.

Resources