hotmart-mcp

hotmart_subscriber_purchases_list

Retrieve all purchases made by a subscriber using their Hotmart subscriber code. Get a list of transactions linked to a specific subscriber.

Instructions

Subscriber Purchases. Example: hotmart_subscriber_purchases_list(subscriber_code='ABC123XY').

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": {
      "subscriber_code": "<subscriber_code>"
    },
    "name": "hotmart_subscriber_purchases_list"
  }
}

Input Schema

Name	Required	Description	Default
`subscriber_code`	Yes	Subscriber code. Format: alphanumeric Hotmart code (ex: `H123A4B5`, not UUID, not int)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.3May 14, 2026

TDQS

C2.3/5.0

Behavior1/5

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

Behavioral traits are completely absent. The description does not disclose if the tool is read-only, requires specific authentication, has rate limits, or returns a subset of transactions. With no annotations, the description should carry this burden but fails entirely.

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 very short (two sentences), but one sentence is just an example. It is not structurally informative; it lacks headings or readability aids. It could be more concise while including more substance.

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?

Despite the presence of an output schema, the description fails to provide contextual completeness. It does not explain what constitutes a purchase, the scope of data returned, or any error conditions. A simple tool with one parameter still benefits from minimal guidance on invocation context.

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?

The input schema provides full parameter description (format examples, constraints). The description adds only an example call, which provides no new semantic meaning beyond the schema. With 100% coverage, baseline 3 is appropriate.

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 'Subscriber Purchases' which conveys the general purpose of listing purchases for a subscriber, but it lacks specificity to distinguish it from sibling tools like hotmart_subscription_transactions_list or hotmart_sales_history_list, which might also involve purchases. The example provides a usage pattern but no differentiation.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it mention any prerequisites or context for invocation.

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

Deploy Server