Skip to main content
Glama

Hotmart

by io.github.mcp-dir
OverviewDiscussionsAdmin

hotmart_subscriptions_write_cancel

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: cancel]

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.2/5.0
Behavior1/5

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

The description says 'cancela 1+ assinaturas', which is a destructive operation, yet the annotations set 'destructiveHint': false. This is a direct contradiction. No additional behavioral traits like authorization requirements or side effects are mentioned.

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

Conciseness3/5

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

The description is relatively concise but includes extraneous information about other actions. The key point (cancel) is mentioned, but the structure could be tighter without listing unrelated capabilities.

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 parameters, nested object, no output schema), the description lacks essential details such as required fields, error handling, return values, and full parameter semantics. It does not compensate for the lack of annotations or schema descriptions.

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 0% schema description coverage, the description carries full burden but only explains a few parameters: send_mail (default true), charge (default false), subscriber_codes. It fails to describe 'data' (a nested object with additionalProperties), 'account', 'due_day', and 'subscriber_code', leaving the agent with incomplete understanding.

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 states it handles mutations on Hotmart subscriptions and specifically mentions 'cancel' as an action, but it also lists other actions (reactivate, change_due_day, switch_plan) that are not relevant to this tool, creating confusion. The title clarifies it is for cancel, but the description's inclusion of multiple actions blurs the purpose.

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 versus its siblings (e.g., hotmart_subscriptions_write_reactivate). The description lists alternative actions but does not indicate that this tool is specifically for cancel, leaving the agent without clear selection criteria.

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