Skip to main content
Glama

get_sales_price_details

Get price details of sales filtered by transaction, status, product, date, or payment type. Without filters, only APPROVED and COMPLETE sales are returned.

Instructions

Sales Price Details

Retorna os detalhes de preço das vendas. Sem os filtros transaction ou transaction_status, apenas vendas com status APPROVED e COMPLETE são retornadas.

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)
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
selectNoSeleção de campos customizados na resposta

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'get_sales_price_details' tool. It accepts optional filter parameters (transaction, transaction_status, max_results, page_token, product_id, start_date, end_date, payment_type, select), builds query params, calls the GET /payments/api/v1/sales/price/details endpoint via the shared HTTP client, and returns the JSON response as a string.
    async def get_sales_price_details(
        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,
        payment_type: Optional[str] = None,
        select: Optional[str] = None,
    ) -> str:
        """Sales Price Details
        
        Retorna os detalhes de preço das vendas. Sem os filtros transaction ou transaction_status, apenas vendas com status APPROVED e COMPLETE são retornadas.
        
        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)
            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
            select: Seleção de campos customizados na resposta"""
        endpoint = "/payments/api/v1/sales/price/details"
        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 payment_type is not None:
            params["payment_type"] = payment_type
        if select is not None:
            params["select"] = select
        result = await get_client().get(endpoint, params=params)
        return json.dumps(result, indent=2)
  • The tool function is explicitly listed in the __all__ export list, making it importable from the sales module.
    __all__ = ["get_sales_history", "get_sales_summary", "get_sales_participants", "get_sales_commissions", "get_sales_price_details", "refund_sale"]
  • Generic dynamic tool registration: all async functions (not starting with '_') from every module under tools_pkg are discovered via pkgutil and registered as FastMCP tools via mcp.tool(). This is where get_sales_price_details gets registered as an MCP tool.
    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
  • Re-exports all definitions from sales.py (including get_sales_price_details) via wildcard import.
    from .sales import *  # noqa: F401,F403
  • Shared helper that provides the HTTP client instance used by the handler to make the API call.
    def get_client() -> HotmartClient:
        global _client
        if _client is None:
            _client = HotmartClient()
        return _client
Behavior3/5

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

With no annotations, the description discloses one key behavior (default status filtering) but omits other traits like pagination behavior, rate limits, or error conditions. The presence of an output schema covers return structure, but the description adds limited behavioral context.

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 two sentences, front-loaded with purpose, and every word adds value. No redundancy or fluff.

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?

Given the tool has 9 parameters and an output schema, the description is minimal. It covers default filtering but lacks details on pagination, field selection, or the meaning of 'price details'. The output schema helps, but the description could be more comprehensive.

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 description coverage is 100%, so each parameter is already explained in the schema. The description adds value for transaction and transaction_status by explaining their interplay with default filters, but does not enhance meaning for the other 7 parameters.

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 it returns 'price details of sales' and specifies a default filter behavior (only APPROVED and COMPLETE status). This distinguishes it from siblings like get_sales_summary or get_sales_commissions, but could be more specific about what constitutes 'price details'.

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

Usage Guidelines3/5

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

The description implicitly guides when to use filters (to override the default status filter) but does not explicitly state when to use this tool over siblings or mention any prerequisites or exclusions.

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