Skip to main content
Glama
Sign In
hotmart-mcp

hotmart-mcp

by thaleslaray
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hotmart_coupon_delete

Delete a Hotmart coupon by providing its unique coupon ID. Removes the coupon from your account to manage promotions.

Instructions

Delete Coupon. Example: hotmart_coupon_delete(coupon_id=12345).

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": {
      "coupon_id": "<coupon_id>"
    },
    "name": "hotmart_coupon_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
coupon_idYesCoupon ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description must cover behavioral traits. It only says 'Delete Coupon' without noting permanence, permissions, or side effects on associated data.

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

Conciseness4/5

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

Extremely concise: one sentence and an example. No wasted words, though slightly more context could help.

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?

Given the low complexity (one parameter, output schema exists), the description covers the basics but misses safety context like deletion irreversibility.

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% for the single parameter 'coupon_id'. The example usage adds minimal value beyond the schema's description.

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 explicitly states 'Delete Coupon' with a concrete example, making the action and resource clear. It distinguishes from sibling tools like hotmart_coupon_create and hotmart_coupons_list.

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 on when to use this tool vs alternatives, no prerequisites or consequences mentioned. Only an example call is provided.

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

Deploy Server

Other Tools