Skip to main content
Glama

hotmart_batch_subscriptions_reactivate

Batch reactivate multiple Hotmart subscriptions by providing a list of subscriber codes. Optionally charge immediately.

Instructions

Batch Reactivate Subscriptions. Use this for multiple subscriber_codes at once. For a single one, prefer hotmart_subscription_reactivate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriber_codeYesList of subscriber codess. Pass a JSON array of strings, e.g. `['ABC123XY', 'DEF456ZW']`.
chargeNoCobrar imediatamente

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Main handler for hotmart_batch_subscriptions_reactivate. Sends POST request to /payments/api/v1/subscriptions/reactivate with a list of subscriber codes and optional charge parameter.
    async def hotmart_batch_subscriptions_reactivate(
        subscriber_code: list[str],
        charge: Optional[bool] = None,
    ) -> str:
        """Batch Reactivate Subscriptions. Use this for multiple subscriber_codes at once. For a single one, prefer `hotmart_subscription_reactivate`.
        
        Args:
            subscriber_code: List of subscriber codess. Pass a JSON array of strings, e.g. `['ABC123XY', 'DEF456ZW']`.
            charge: Cobrar imediatamente"""
        endpoint = "/payments/api/v1/subscriptions/reactivate"
        body = {}
        body["subscriber_code"] = subscriber_code
        if charge is not None:
            body["charge"] = charge
        result = await get_client().post(endpoint, json=body)
        return json.dumps(result, indent=2)
  • Auto-discovery registration: iterates over all modules in hotmart_mcp.tools and registers every async function (that doesn't start with '_') as a FastMCP tool via mcp.tool()(obj). This automatically registers hotmart_batch_subscriptions_reactivate.
    def _discover_and_register_tools() -> int:
        """Import all modules under hotmart_mcp.tools and register async functions."""
        registered = 0
        for module_info in pkgutil.iter_modules(tools_pkg.__path__, prefix=f"{tools_pkg.__name__}."):
            if module_info.name.endswith("__init__"):
                continue
            module = importlib.import_module(module_info.name)
            for name, obj in inspect.getmembers(module, iscoroutinefunction):
                if name.startswith("_"):
                    continue
                mcp.tool()(obj)
                registered += 1
        return registered
  • Disambiguation description for the tool: 'Use this for multiple subscriber_codes at once. For a single one, prefer hotmart_subscription_reactivate.'
    "hotmart_batch_subscriptions_reactivate":
        "Use this for multiple subscriber_codes at once. For a single one, prefer `hotmart_subscription_reactivate`.",
  • Exported in __all__ of the subscriptions module, making it discoverable.
    __all__ = ["hotmart_subscriptions_list", "hotmart_subscriptions_summary_list", "hotmart_subscription_transactions_list", "hotmart_subscriber_purchases_list", "hotmart_subscription_cancel", "hotmart_batch_subscriptions_cancel", "hotmart_subscription_reactivate", "hotmart_batch_subscriptions_reactivate", "hotmart_subscription_due_day_update"]
Behavior2/5

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

No annotations are provided, and the description only says 'Batch Reactivate Subscriptions' without disclosing behavioral traits like idempotency, partial failure handling, or authentication requirements. The charge parameter is mentioned briefly (Cobrar imediatamente) but not elaborated.

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?

Two sentences, very concise and front-loaded with the core purpose. Every word earns its place.

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?

With an output schema present, return values are handled. However, for a batch operation, more context about behavior (e.g., partial success, errors) would be beneficial. The description is minimal but sufficient for a simple batch tool.

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%, and the description adds little beyond restating that it's for multiple subscriber_codes. The schema already describes the parameters adequately, so the description does not significantly enhance meaning.

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 (Batch Reactivate), the resource (Subscriptions), and specifically distinguishes from the sibling tool `hotmart_subscription_reactivate` for single subscriptions.

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 when to use this tool (multiple subscriber_codes) and when not to (single code), and names the preferred alternative, providing clear guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thaleslaray/hotmart-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server