hotmart-mcp

hotmart_subscription_reactivate

Reactivate a single Hotmart subscription using the subscriber code. Optionally, set charge to true to bill immediately.

Instructions

Reactivate Subscription. Example: hotmart_subscription_reactivate(subscriber_code='ABC123XY'). Use this for ONE subscriber_code. For 2+, use hotmart_batch_subscriptions_reactivate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subscriber_code": "<subscriber_code>"
    },
    "name": "hotmart_subscription_reactivate"
  }
}

Input Schema

Name	Required	Description	Default
`subscriber_code`	Yes	Subscriber code. Format: alphanumeric Hotmart code (ex: `H123A4B5`, not UUID, not int)
`charge`	No	Cobrar imediatamente

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.3May 14, 2026

TDQS

A3.9/5.0

Behavior2/5

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

No annotations provided, so description bears full burden. It does not disclose side effects, permissions, or what the charge parameter does (Portuguese only). Only the basic action is stated.

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?

Extremely concise: two sentences and an example. No wasted words; all sentences are essential.

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

Completeness3/5

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

Output schema exists, so return values don't need explanation. However, for a mutation tool with no annotations, more behavioral context (e.g., what charge=true does) would improve completeness. The current description is functional but minimal.

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?

Schema coverage is 100%, baseline is 3. Description does not add meaning beyond schema; the charge parameter's effect is not explained in English, and no additional context for subscriber_code is given.

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 clearly states the action (Reactivate Subscription) and resource, with an example and explicit differentiation from the batch sibling tool. The verb and resource are specific and distinct.

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

Usage Guidelines5/5

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

Explicitly states to use for one subscriber_code and directs to hotmart_batch_subscriptions_reactivate for multiple, providing clear when-to-use and when-not-to-use guidance.

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

Deploy Server