Skip to main content
Glama

Hotmart

by io.github.mcp-dir
OverviewDiscussionsAdmin

hotmart_subscriptions_write_reactivate

Mutações em assinaturas Hotmart. Ações:

  • cancel: cancela 1+ assinaturas (subscriber_codes[]). send_mail (default true) avisa o assinante.

  • reactivate: reativa 1+ assinaturas (subscriber_codes[]). charge (default false) cobra na hora.

  • change_due_day: muda o dia de cobrança de UMA assinatura (subscriber_code + due_day 1-31).

  • switch_plan: troca o plano de uma assinatura (data com subscriber_code + novo plano, conforme doc).

[Flattened action: reactivate]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
chargeNo
accountNo
due_dayNo
send_mailNo
subscriber_codeNo
subscriber_codesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / data
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedInput schema / properties / due_day
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / subscriber_code
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "subscriber_codes"
-]
  2. First observed

TDQS

C2.4/5.0
Behavior3/5

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

The description mentions that charge defaults to false and that reactivate works on one or more subscriptions, but does not disclose potential side effects, idempotency, or failure modes. Annotations only show readOnlyHint=false and destructiveHint=false, so the description adds some context but not enough.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description includes a list of actions not relevant to this specific tool, making it longer than necessary. The key information that this tool is for reactivate is placed at the end as a note, not front-loaded.

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

Completeness2/5

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

Given the complexity (7 params, nested object, no output schema, no annotations), the description fails to explain prerequisites, authentication, error handling, or expected outcomes. It is incomplete for an agent to correctly use the tool.

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

Parameters2/5

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

With 7 parameters and 0% schema description coverage, the description only names a few parameters (subscriber_codes, charge, send_mail, subscriber_code, due_day) without explaining their usage, relationships, or constraints. The 'data' parameter is not explained at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists multiple actions (cancel, reactivate, change_due_day, switch_plan), which suggests a general subscription mutation tool, but the title and final line indicate this tool is specifically for reactivate. This makes the purpose unclear for the agent.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool vs. sibling tools like hotmart_subscriptions_write_cancel or hotmart_subscriptions_write_switch_plan. The description does not explicitly state that this tool handles only reactivate.

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

All Hotmart toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources