Skip to main content
Glama

get_sales_summary

Retrieve a summarized overview of sales transactions with filtering options by status, product, date, affiliate, and payment type.

Instructions

Sales Summary

Retorna o resumo das vendas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transactionNoCódigo da transação
transaction_statusNoStatus da transação. Values: APPROVED, BLOCKED, CANCELLED, CHARGEBACK, COMPLETE, EXPIRED, NO_FUNDS, OVERDUE, PARTIALLY_REFUNDED, PRE_ORDER, PRINTED_BILLET, PROCESSING_TRANSACTION, PROTESTED, REFUNDED, STARTED, UNDER_ANALISYS, WAITING_PAYMENT
max_resultsNoNúmero máximo de resultados por página
page_tokenNoToken de paginação para a próxima página
product_idNoID do produto
start_dateNoData inicial (timestamp em milissegundos desde epoch)
end_dateNoData final (timestamp em milissegundos desde epoch)
sales_sourceNoOrigem da venda
affiliate_nameNoNome do afiliado
payment_typeNoTipo de pagamento. Values: BILLET, CASH_PAYMENT, CREDIT_CARD, DIRECT_BANK_TRANSFER, DIRECT_DEBIT, FINANCED_BILLET, FINANCED_INSTALLMENT, GOOGLE_PAY, HOTCARD, HYBRID, MANUAL_TRANSFER, PAYPAL, PAYPAL_INTERNACIONAL, PICPAY, PIX, SAMSUNG_PAY, WALLET
offer_codeNoCódigo da oferta
selectNoSeleção de campos customizados na resposta

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the get_sales_summary tool. Calls the Hotmart API endpoint /payments/api/v1/sales/summary with optional query parameters and returns JSON.
    async def get_sales_summary(
        transaction: Optional[str] = None,
        transaction_status: Optional[str] = None,
        max_results: Optional[int] = None,
        page_token: Optional[str] = None,
        product_id: Optional[int] = None,
        start_date: Optional[int] = None,
        end_date: Optional[int] = None,
        sales_source: Optional[str] = None,
        affiliate_name: Optional[str] = None,
        payment_type: Optional[str] = None,
        offer_code: Optional[str] = None,
        select: Optional[str] = None,
    ) -> str:
        """Sales Summary
        
        Retorna o resumo das vendas.
        
        Args:
            transaction: Código da transação
            transaction_status: Status da transação. Values: APPROVED, BLOCKED, CANCELLED, CHARGEBACK, COMPLETE, EXPIRED, NO_FUNDS, OVERDUE, PARTIALLY_REFUNDED, PRE_ORDER, PRINTED_BILLET, PROCESSING_TRANSACTION, PROTESTED, REFUNDED, STARTED, UNDER_ANALISYS, WAITING_PAYMENT
            max_results: Número máximo de resultados por página
            page_token: Token de paginação para a próxima página
            product_id: ID do produto
            start_date: Data inicial (timestamp em milissegundos desde epoch)
            end_date: Data final (timestamp em milissegundos desde epoch)
            sales_source: Origem da venda
            affiliate_name: Nome do afiliado
            payment_type: Tipo de pagamento. Values: BILLET, CASH_PAYMENT, CREDIT_CARD, DIRECT_BANK_TRANSFER, DIRECT_DEBIT, FINANCED_BILLET, FINANCED_INSTALLMENT, GOOGLE_PAY, HOTCARD, HYBRID, MANUAL_TRANSFER, PAYPAL, PAYPAL_INTERNACIONAL, PICPAY, PIX, SAMSUNG_PAY, WALLET
            offer_code: Código da oferta
            select: Seleção de campos customizados na resposta"""
        endpoint = "/payments/api/v1/sales/summary"
        params = {}
        if transaction is not None:
            params["transaction"] = transaction
        if transaction_status is not None:
            params["transaction_status"] = transaction_status
        if max_results is not None:
            params["max_results"] = max_results
        if page_token is not None:
            params["page_token"] = page_token
        if product_id is not None:
            params["product_id"] = product_id
        if start_date is not None:
            params["start_date"] = start_date
        if end_date is not None:
            params["end_date"] = end_date
        if sales_source is not None:
            params["sales_source"] = sales_source
        if affiliate_name is not None:
            params["affiliate_name"] = affiliate_name
        if payment_type is not None:
            params["payment_type"] = payment_type
        if offer_code is not None:
            params["offer_code"] = offer_code
        if select is not None:
            params["select"] = select
        result = await get_client().get(endpoint, params=params)
        return json.dumps(result, indent=2)
  • Input schema/type annotations for the get_sales_summary function — all parameters are Optional with str or int types, returning str.
    async def get_sales_summary(
        transaction: Optional[str] = None,
        transaction_status: Optional[str] = None,
        max_results: Optional[int] = None,
        page_token: Optional[str] = None,
        product_id: Optional[int] = None,
        start_date: Optional[int] = None,
        end_date: Optional[int] = None,
        sales_source: Optional[str] = None,
        affiliate_name: Optional[str] = None,
        payment_type: Optional[str] = None,
        offer_code: Optional[str] = None,
        select: Optional[str] = None,
  • Auto-discovery registration: iterates all tool modules and registers every async function (including get_sales_summary) via FastMCP's mcp.tool() decorator.
    def _discover_and_register_tools() -> int:
        """Import all modules under hotmart_mcp.tools and register async functions."""
        registered = 0
    
        for module_info in pkgutil.iter_modules(tools_pkg.__path__, prefix=f"{tools_pkg.__name__}."):
            if module_info.name.endswith("__init__"):
                continue
    
            module = importlib.import_module(module_info.name)
    
            for name, obj in inspect.getmembers(module, iscoroutinefunction):
                if name.startswith("_"):
                    continue
                mcp.tool()(obj)
                registered += 1
    
        return registered
  • Shared helper: get_client() returns a singleton HotmartClient instance used by get_sales_summary to make the API call.
    _client: HotmartClient | None = None
    
    
    def get_client() -> HotmartClient:
        global _client
        if _client is None:
            _client = HotmartClient()
        return _client
  • Module-level __all__ export listing get_sales_summary as a publicly exported tool function from the sales module.
    __all__ = ["get_sales_history", "get_sales_summary", "get_sales_participants", "get_sales_commissions", "get_sales_price_details", "refund_sale"]
Behavior2/5

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

No annotations are present, so the description carries full burden for behavioral disclosure. It only states 'returns the sales summary' without mentioning read-only nature, authentication requirements, rate limits, or pagination behavior. This is insufficient for a tool with 12 parameters and implied side effects.

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?

The description is very short and to the point, consisting of two lines. However, the first line 'Sales Summary' is redundant and could be removed. Overall, it is concise but not optimally structured.

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?

Given the complexity (12 parameters, many siblings, output schema), the description is severely lacking. It does not define what constitutes a sales summary, what data is aggregated, or how filtering works. The output schema helps but does not substitute for a high-level explanation.

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 baseline is 3. The description adds no information about parameters beyond what the schema provides. It does not explain how parameters like start_date or sales_source affect the summary.

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?

The description clearly states the tool returns a sales summary, using a specific verb ('returns') and resource ('sales summary'). However, it does not differentiate from similar sibling tools like get_sales_history or get_sales_commissions, which may also return sales-related data.

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 guidance is provided on when to use this tool versus alternatives. With many sibling tools (e.g., get_sales_commissions, get_sales_history), the lack of usage context forces the agent to rely on other means to choose appropriately.

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