clickmax-seller-subscriptions

As tools abaixo aparecem com os nomes que o MCP da Clickmax registra. Se o seu cliente de IA prefixar nomes de tool (mcp<servidor>, mcp<servidor>, ou outro), use o nome já prefixado que aparecer na sua lista de tools.

When this applies

Use this skill for seller-side recurring subscriptions: inspect one subscription, filter/chart cohorts, swap the customer's billing card, or cancel one subscription.

Mutations here are always single-subscription: there is no bulk cancel and no renew. Reactivating a canceled subscription means the customer subscribes again through checkout.

Not this skill:

• workspace Clickmax SaaS plan billing -> use the direct plan and buyer billing tools

Key assumptions

• this is about end-customer subscriptions the workspace sells, not the workspace's own SaaS plan
• update-card is idempotent for the same card choice, but it is not a low-stakes edit: it repoints a live recurring charge, so the next renewal bills whoever owns the new card. Treat it as a money action and confirm the target subscription and card before calling
• cancel is permanent at the processor and applies to exactly one subscription
• a cohort can be listed and charted, but not mutated in one call; acting on many subscriptions means one call per subscription, each confirmed

Thought process

1. Confirm which subscription scope the user means: customer subscription vs workspace SaaS plan.
2. For destructive or billing-instrument changes, make the requested action explicit before mutating — name the subscription and the customer, not just the id.

Execute guide

• Use subscriptions_get with id = subscription id to inspect one subscription.
• Use subscriptions_list with page, perPage, and the needed filters such as searchText, subscriptionStatus, productIds, column, and order to find one customer or a cohort.
• Use subscriptions_chart with transactionStatus and membershipPeriod.from/to for counts and trend views inside a billing or membership window.
• Use subscriptionsupdatecard with id and cardId to swap the billing card for one subscription, after the user confirmed which subscription and which card.
• Use subscriptions_cancel with id, cancellationReason, and optional cancellationReasonDescription to cancel one subscription.

• Default order:

1. inspect or list first when the user did not provide an exact subscription id 2. use subscriptionschart for counts/trends, not record-by-record inspection 3. use subscriptionsupdatecard or subscriptionscancel on one subscription at a time

Report

• Start with the scope assumed: one subscription or a product-level cohort.
• For inspection, report status, product, customer match, and key lifecycle dates.
• For charts/lists, summarize the cohort first and then show the most relevant statuses or counts.
• For mutations, report the exact action completed and the subscription it affected.
• Treat follow-up actions as opt-in only.

Warnings

• Do not mix this surface with SaaS workspace plan billing.
• A cohort listing is not an action target: cancelling what a filter returned still requires one confirmed call per subscription.

Anti-patterns

• Canceling when the user only wants to inspect or pause conceptually.
• Using the SaaS plan tools for customer subscription problems.
• Promising a bulk cancel or a renew; neither exists on this surface.