Skip to main content
Glama

hotmart_sales_commissions_list

List Hotmart sales commissions with filters for product, date range, transaction, commission role, and status to retrieve commission data.

Instructions

Sales Commissions. Example: hotmart_sales_commissions_list(max_results=10).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoMax results per page
page_tokenNoPagination token for the next page
product_idNoProduct ID
start_dateNoStart date. 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_dateNoEnd date. Unix timestamp in **milliseconds** (not seconds, not ISO). Ex: `1730419200000` = 2024-11-01 00:00 UTC. Python: `int(datetime(2024,11,1).timestamp() * 1000)`.
transactionNoTransaction code
commission_asNoAuthenticated user's commission role. Allowed values: 'PRODUCER', 'COPRODUCER', 'AFFILIATE'
transaction_statusNoTransaction status.
selectNoCustom field selection in response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No annotations and no description of behavioral traits such as read-only, destructive actions, rate limits, or data scope. The description is silent on these.

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

Conciseness2/5

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

Extremely short but under-informative. The example sentence is minimal and doesn't convey essential context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters, no output schema details, and no behavioral transparency, the description is severely incomplete, leaving the agent without sufficient context to use the tool correctly.

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%, so the description doesn't need to add parameter details. However, it adds no value beyond what's in the schema, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description merely states 'Sales Commissions' which is vague and does not specify the action (list, get?) or distinguish from siblings. The example shows a call but lacks a clear verb.

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

Usage Guidelines1/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 siblings. There are many list tools on the server, but no differentiation provided.

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