Skip to main content
Glama

hotmart_commissions_dashboard_app

View commissions dashboard with total payable/receivable per affiliate, including role and value details. Use to manage monthly commissions and affiliate payouts.

Instructions

Painel de comissões — total a pagar/receber por afiliado.

DataTable com afiliado/papel/valor + Metric de total. Use pra 'comissões do mês', 'quanto pagar pros afiliados', 'settlement'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNoStart date. Unix timestamp in milliseconds.
end_dateNoEnd date. Unix timestamp in milliseconds.
commission_asNoPRODUCER | COPRODUCER | AFFILIATE.
Behavior2/5

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

No annotations provided, and description does not disclose behavioral traits like read-only, destructive actions, rate limits, or auth requirements. Only implies it's a dashboard, likely read-only, but not explicit.

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?

Description is short and front-loaded, but second sentence is fragmented. Overall efficient, no wasted words.

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?

Despite no output schema, description gives high-level output structure (DataTable and Metric) and use cases. Missing details like return format, pagination, or behavior with null parameters, which are left to the schema. Adequate but not fully 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?

Schema covers all parameters with 100% description coverage. Description does not add additional semantic meaning beyond what schema already provides (dates as Unix timestamps, commission_as values). Baseline 3 is appropriate.

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

Purpose4/5

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

Description clearly states it's a commissions dashboard showing totals to pay/receive per affiliate, with DataTable and metric. It distinguishes from many sibling tools by focusing on commissions, but does not explicitly differentiate from similar tools like hotmart_sales_commissions_list.

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

Usage Guidelines4/5

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

Provides specific use cases: 'comissões do mês', 'quanto pagar pros afiliados', 'settlement'. Gives context for when to use, but no explicit when-not or alternatives.

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