write_product_catalog
write_product_catalog
Live server: test server (test.mcp.solvimon.com) only.
Defines the catalog structure and charge type, and manages coupons and promotion codes. Hierarchy: product category (optional) → product → product items and features.
Actions: create, update, delete, activate, deactivate, archive, deprecate. Lifecycle actions apply to products, product items, coupons and promotion codes; deactivate to coupons and promotion codes only.
Resource types: product_categories, products, product_items, features, coupons, promotion_codes
Product item model_type options: RECURRING, PER_SEAT, USAGE_BASED (needs a meter_value_calculation_id), ONE_OFF, CREDITS (needs a credit_type_id). Features are non-billable entitlements such as rate limits or feature flags (NUMBER, AMOUNT, ENUM, SWITCH).
Coupons and promotion codes.
- A coupon is always created DRAFT. The result has a summary to confirm before
activate. - If a coupon with the same discount, duration and scope already exists, the create is refused and the existing one is named so you can reuse it. Pass
allow_duplicate_terms: trueto create it anyway. - A coupon’s terms can’t be edited. Create a replacement and
deactivatethe old one. Deactivating stops new redemptions; existing holders keep the discount. - A promotion code needs an ACTIVE coupon and can only narrow it.
model_type is immutable after creation. Creating a product requires category_id, product_type (e.g. DEFAULT) and billing_entity_id alongside name and reference. Guidance (agent_context) or a description in the body is proposed first and saved only with text_confirmed: true, see write_agent_context.