Skip to main content
Glama

hotmart_subscription_transactions_list

Retrieve detailed transaction records for Hotmart subscriptions. Filter by product, subscriber, date range, status, and billing type.

Instructions

Subscription Transactions. Example: hotmart_subscription_transactions_list(max_results=10). Don't use this for the subscription list itself — use hotmart_subscriptions_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoMax results per page
page_tokenNoPagination token for the next page
product_idNoProduct ID
transactionNoTransaction code
subscriber_nameNoNome do assinante
subscriber_emailNoEmail do assinante
billing_typeNoTipo de cobrança. Allowed values: 'SUBSCRIPTION', 'SMART_INSTALLMENT', 'SMART_RECOVERY'
subscription_statusNoSubscription status.
recurrency_statusNoStatus da recorrência.
purchase_statusNoStatus da compra
transaction_dateNoData da transação inicial. Unix timestamp in **milliseconds** (not seconds, not ISO). Ex: `1730419200000` = 2024-11-01 00:00 UTC. Python: `int(datetime(2024,11,1).timestamp() * 1000)`.
end_transaction_dateNoData da transação final. Unix timestamp in **milliseconds** (not seconds, not ISO). Ex: `1730419200000` = 2024-11-01 00:00 UTC. Python: `int(datetime(2024,11,1).timestamp() * 1000)`.
offer_codeNoOffer code. Format: alphanumeric Hotmart code (ex: `H123A4B5`, not UUID, not int)
purchase_payment_typeNoPayment type da compra.
subscriber_codeNoSubscriber code. Format: alphanumeric Hotmart code (ex: `H123A4B5`, not UUID, not int)
selectNoCustom field selection in response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description fully bears the burden of behavioral disclosure. However, it only repeats the tool's purpose and gives an example, without mentioning idempotency, rate limits, pagination behavior, or side effects. The description adds minimal behavioral context beyond the obvious.

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

Conciseness5/5

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

The description is extremely concise: two sentences that cover purpose, example, and a sibling distinction. Every sentence is necessary and no word is wasted.

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?

The tool is complex with 16 parameters, but the description is minimal. With an output schema present (as indicated), the description does not need to detail return values. However, it lacks context on pagination, filtering, and typical use cases beyond the example. Adequate but could be more complete.

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 has 100% coverage with descriptions for all 16 parameters, including detailed notes (e.g., transaction_date explains the milliseconds format). The tool description only shows an example using max_results, but does not add new meaning beyond what the schema already provides. The baseline is 3 given the high schema coverage.

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 clearly states 'Subscription Transactions' and gives an example usage. It also distinguishes from the sibling tool hotmart_subscriptions_list by explicitly saying not to use this for the subscription list itself.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when not to use the tool ('Don't use this for the subscription list itself') and directs to the correct sibling tool (hotmart_subscriptions_list). This is a clear alternative and context for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thaleslaray/hotmart-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server