Mutações em cupons de desconto Hotmart. Ações:
create: cria um cupom num produto (product_id + code + discount decimal 0-1, ex.: 0.1 = 10%).
delete: remove um cupom (coupon_id).
[Flattened action: delete]
Bulk support: accepts product_ids, coupon_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| account | No | ||
| discount | No | ||
| coupon_id | No | ||
| coupon_ids | No | ||
| product_id | No | ||
| product_ids | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description states delete removes a coupon (destructive), but annotations set destructiveHint=false, creating a contradiction. No other behavioral context (e.g., permissions, idempotency) is provided.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is brief but poorly structured. The 'Ações' list and '[Flattened action: delete]' note are confusing and could be more coherent. Redundancy and lack of logical flow reduce effectiveness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description does not explain return values. With 7 parameters and mixed actions, the description is insufficient for an agent to correctly invoke the tool without guessing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description adds meaning for some parameters (e.g., discount decimal range, bulk fields), but the 'account' parameter is unexplained, and the mapping of parameters to create vs delete actions is ambiguous.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states it performs mutations (create/delete) on Hotmart coupons, but the addition of '[Flattened action: delete]' creates confusion about whether this tool actually handles both or only delete. The sibling 'hotmart_coupons_write_create' suggests the delete-only interpretation, reducing clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus siblings like hotmart_coupons_write_create or hotmart_coupons. Mention of bulk support gives some context but does not differentiate from alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.