Skip to main content
Glama
anythink-cloud

Anythink-MCP

Official

Pay: offers create

pay_offers_create

Create discount, trial extension, or referral offers with required redeemer rewards; set optional referrer rewards, eligibility, caps, and dates. Discount offers also create Stripe coupons.

Instructions

Create an offer (rewards via convenience flags or raw JSON). Creates an offer of kind discount, trial_extension or referral. A redeemer reward is required, as raw JSON or a shortcut such as trial days or discount percent; referrer reward, eligibility, caps and dates are optional. Discount offers also create a Stripe coupon. Add a code users can enter with pay_offers_add_code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoOffer kind: discount, trial_extension, or referral
nameNoOffer display name
statusNoInitial status: active (default), paused, or expired
total_capNoTotal redemption cap (omit for unlimited)
valid_fromNoOffer valid-from (ISO date/time)
descriptionNoOffer description
eligibilityNoEligibility rules as JSON, e.g. {"match":"all","rules":[{"type":"subscribed_to_plan","plan_ids":[1]}]}
valid_untilNoOffer valid-until (ISO date/time)
per_user_capNoPer-user redemption cap (default 1)
redeemer_rewardNoRedeemer reward as JSON, e.g. {"type":"discount","percent_off":50,"duration":"once"}
referrer_rewardNoReferrer reward as JSON (referral offers only)
discount_percentNoShortcut: redeemer reward = N% discount (use --discount-duration for recurrence)
discount_durationNoDiscount duration for --discount-percent: once, forever, repeating (default once)
redeemer_trial_daysNoShortcut: redeemer reward = trial extension of N days
referrer_trial_daysNoShortcut: referrer reward = trial extension of N days
referrer_subscription_daysNoShortcut: referrer reward = subscription extension of N days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.37

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive write. The description adds genuinely useful behavior beyond that: discount offers also create a Stripe coupon (an external side effect), and it clarifies the required/optional structure of the payload. This is real added context, though it omits error conditions or permission requirements.

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?

Four sentences, each carrying distinct payload: purpose, kinds, required/optional structure, and the Stripe-coupon plus next-step pointer. Front-loaded and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter mutation tool with no output schema, the description covers the required field, the shortcut-vs-JSON duality, the side effect of coupon creation, and the logical next step. Combined with full schema coverage and annotations, an agent has enough to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds conceptual meaning on top: it identifies redeemer_reward as required, explains that rewards can be given either as raw JSON or via shortcut flags (discount_percent, trial days), and notes referrer reward applies only to referral offers. Useful framing beyond the per-field schema text.

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?

States a specific verb (Create) and resource (an offer), then enumerates the three offer kinds (discount, trial_extension, referral). This distinguishes it cleanly from siblings like pay_offers_update, pay_offers_add_code, and pay_offers_activate without opening any schema.

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

Usage Guidelines4/5

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

Explains what is required (a redeemer reward) versus optional (referrer reward, eligibility, caps, dates) and routes the agent to pay_offers_add_code for the follow-up step of attaching a code. It does not explicitly contrast when to reach for this versus update or activate, so it falls just short of a 5.

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

Deploy Server

Other Tools