create_couponsMUTATES Memberful data: create one or more coupon codes for a discount. Provide the discount id (discountId) and the coupon code strings. Memberful GraphQL: createCoupons(discountId, coupons).
| Name | Required | Description | Default |
|---|---|---|---|
| codes | Yes | Coupon code strings to create (at least one, required). | |
| discountId | No | The discount id to attach the coupons to. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly opens with 'MUTATES Memberful data', which aligns with and reinforces the destructiveHint annotation. It also reveals the underlying GraphQL operation, adding useful behavioral context beyond the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no wasted words. The safety-relevant 'MUTATES' signal is front-loaded, and the required inputs and GraphQL mapping are stated efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple mutation tool with fully documented parameters and a destructiveHint annotation, the description gives enough to invoke it correctly. It could mention return values or error behavior, but nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 both parameters. The description adds a small amount of relational context by naming the GraphQL mapping, but does not significantly increase semantic clarity beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action: create one or more coupon codes for a discount, with the required inputs. It is distinct from sibling tools, none of which specifically create coupons.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: use this when creating coupon codes, and provides the necessary inputs (discountId and codes). It does not explicitly name alternatives or exclusions, but the usage is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools map cleanly to a resource-action pair: members, subscriptions, plans, passes, and coupons. The main ambiguity is between list_passes and list_plans, and the two GraphQL escape hatches intentionally overlap with every dedicated tool, though their descriptions make the boundaries fairly clear.
Tools follow a predictable snake_case verb_noun pattern: create_, get_, list_, update_, and change_ are used consistently for the curated operations. The exceptions are memberful_graphql and memberful_query, which use a different naming style, and change_subscription_expiration uses 'change' instead of 'update'.
Twelve tools is a well-scoped size for a Memberful integration. The curated tools cover the main resources, and the two escape hatches provide flexible coverage without needing dozens of narrow tools.
The curated tools cover member creation/reading/updating, subscription retrieval, coupon creation, and plan/pass listing. However, important lifecycle operations like cancelling or modifying subscriptions, deleting members, and managing plans are only available through the generic memberful_graphql escape hatch rather than dedicated tools.