Skip to main content
Glama

list_products

Retrieve a list of Hotmart products with optional filters by status, format, ID, and pagination to manage product catalog.

Instructions

List Products

Retorna a lista de produtos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoNúmero máximo de resultados por página
page_tokenNoToken de paginação para a próxima página
id_NoID do produto
statusNoStatus do produto. Values: DRAFT, ACTIVE, PAUSED, NOT_APPROVED, IN_REVIEW, DELETED, CHANGES_PENDING_ON_PRODUCT
format_NoFormato do produto. Values: EBOOK, SOFTWARE, MOBILE_APPS, VIDEOS, AUDIOS, TEMPLATES, IMAGES, ONLINE_COURSE, SERIAL_CODES, ETICKET, ONLINE_SERVICE, ONLINE_EVENT, BUNDLE, COMMUNITY
selectNoSeleção de campos customizados na resposta

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function for the 'list_products' tool. Makes an HTTP GET request to /products/api/v1/products with optional filters (max_results, page_token, id_, status, format_, select) and returns the JSON response.
    async def list_products(
        max_results: Optional[int] = None,
        page_token: Optional[str] = None,
        id_: Optional[int] = None,
        status: Optional[str] = None,
        format_: Optional[str] = None,
        select: Optional[str] = None,
    ) -> str:
        """List Products
        
        Retorna a lista de produtos.
        
        Args:
            max_results: Número máximo de resultados por página
            page_token: Token de paginação para a próxima página
            id_: ID do produto
            status: Status do produto. Values: DRAFT, ACTIVE, PAUSED, NOT_APPROVED, IN_REVIEW, DELETED, CHANGES_PENDING_ON_PRODUCT
            format_: Formato do produto. Values: EBOOK, SOFTWARE, MOBILE_APPS, VIDEOS, AUDIOS, TEMPLATES, IMAGES, ONLINE_COURSE, SERIAL_CODES, ETICKET, ONLINE_SERVICE, ONLINE_EVENT, BUNDLE, COMMUNITY
            select: Seleção de campos customizados na resposta"""
        endpoint = "/products/api/v1/products"
        params = {}
        if max_results is not None:
            params["max_results"] = max_results
        if page_token is not None:
            params["page_token"] = page_token
        if id_ is not None:
            params["id"] = id_
        if status is not None:
            params["status"] = status
        if format_ is not None:
            params["format"] = format_
        if select is not None:
            params["select"] = select
        result = await get_client().get(endpoint, params=params)
        return json.dumps(result, indent=2)
  • Type hints and docstring defining the input schema/parameters for list_products (max_results, page_token, id_, status, format_, select).
    Args:
        max_results: Número máximo de resultados por página
        page_token: Token de paginação para a próxima página
        id_: ID do produto
        status: Status do produto. Values: DRAFT, ACTIVE, PAUSED, NOT_APPROVED, IN_REVIEW, DELETED, CHANGES_PENDING_ON_PRODUCT
        format_: Formato do produto. Values: EBOOK, SOFTWARE, MOBILE_APPS, VIDEOS, AUDIOS, TEMPLATES, IMAGES, ONLINE_COURSE, SERIAL_CODES, ETICKET, ONLINE_SERVICE, ONLINE_EVENT, BUNDLE, COMMUNITY
        select: Seleção de campos customizados na resposta"""
    endpoint = "/products/api/v1/products"
    params = {}
    if max_results is not None:
        params["max_results"] = max_results
    if page_token is not None:
        params["page_token"] = page_token
    if id_ is not None:
        params["id"] = id_
    if status is not None:
        params["status"] = status
    if format_ is not None:
        params["format"] = format_
    if select is not None:
  • Dynamic tool registration in _discover_and_register_tools(). Scans all modules under hotmart_mcp.tools and registers every public async function (including list_products) with 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
  • The get_client() helper used by list_products to obtain a shared HotmartClient singleton instance.
    def get_client() -> HotmartClient:
        global _client
        if _client is None:
            _client = HotmartClient()
        return _client
  • The HotmartClient.get() method that list_products calls internally to execute the HTTP GET request.
    async def get(
        self,
        path: str,
        params: dict[str, Any] | None = None,
        select: list[str] | None = None,
    ) -> dict[str, Any]:
        return await self._request("GET", path, params=params, select=select)
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It fails to mention that the tool is read-only, supports pagination, or any limitations. The minimal description does not disclose behavioral traits beyond listing.

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 concise with two short sentences and front-loaded with the title. It is efficient, though it could be slightly expanded with contextual information without losing conciseness.

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 presence of an output schema and six optional parameters, the description is somewhat insufficient. It does not mention pagination, filtering, or selection capabilities, which are all present in the schema but could be summarized for completeness.

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?

Since schema description coverage is 100%, the description adds no additional meaning beyond the parameter descriptions in the schema. The baseline score of 3 is appropriate as the schema already documents parameter semantics.

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 'List Products' and 'Retorna a lista de produtos,' indicating the tool lists products. However, it does not elaborate on filtering or sorting capabilities beyond what the schema provides, which reduces specificity.

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?

No guidance is given on when to use this tool versus alternatives. While there are no sibling product listing tools, the description could mention that it is the primary tool for listing products with optional filters.

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