Skip to main content
Glama

hotmart_products_list

List Hotmart products with filters for status, format, and pagination to manage your catalog.

Instructions

List Products. Example: hotmart_products_list(max_results=10).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoMax results per page
page_tokenNoPagination token for the next page
id_NoProduct ID
statusNoStatus do produto.
format_NoFormato do produto.
selectNoCustom field selection in response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for hotmart_products_list. It accepts optional parameters (max_results, page_token, id_, status, format_, select), builds query params, and calls the GET /products/api/v1/products endpoint via the shared HotmartClient.
    async def hotmart_products_list(
        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. Example: hotmart_products_list(max_results=10).
        
        Args:
            max_results: Max results per page
            page_token: Pagination token for the next page
            id_: Product ID
            status: Status do produto.
            Allowed values (case-sensitive, pass EXACTLY as listed):
              - `DRAFT`
              - `ACTIVE`
              - `PAUSED`
              - `NOT_APPROVED`
              - `IN_REVIEW`
              - `DELETED`
              - `CHANGES_PENDING_ON_PRODUCT`
            format_: Formato do produto.
            Allowed values (case-sensitive, pass EXACTLY as listed):
              - `EBOOK`
              - `SOFTWARE`
              - `MOBILE_APPS`
              - `VIDEOS`
              - `AUDIOS`
              - `TEMPLATES`
              - `IMAGES`
              - `ONLINE_COURSE`
              - `SERIAL_CODES`
              - `ETICKET`
              - `ONLINE_SERVICE`
              - `ONLINE_EVENT`
              - `BUNDLE`
              - `COMMUNITY`
            select: Custom field selection in response"""
        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)
  • ProductStatus and ProductFormat StrEnum types define the allowed enum values for the status and format_ parameters of hotmart_products_list.
    class ProductStatus(StrEnum):
        """
        Status do produto
        """
    
        DRAFT = 'DRAFT'
        ACTIVE = 'ACTIVE'
        PAUSED = 'PAUSED'
        NOT_APPROVED = 'NOT_APPROVED'
        IN_REVIEW = 'IN_REVIEW'
        DELETED = 'DELETED'
        CHANGES_PENDING_ON_PRODUCT = 'CHANGES_PENDING_ON_PRODUCT'
    
    
    class ProductFormat(StrEnum):
        """
        Formato do produto
        """
    
        EBOOK = 'EBOOK'
        SOFTWARE = 'SOFTWARE'
        MOBILE_APPS = 'MOBILE_APPS'
        VIDEOS = 'VIDEOS'
        AUDIOS = 'AUDIOS'
        TEMPLATES = 'TEMPLATES'
        IMAGES = 'IMAGES'
        ONLINE_COURSE = 'ONLINE_COURSE'
        SERIAL_CODES = 'SERIAL_CODES'
        ETICKET = 'ETICKET'
        ONLINE_SERVICE = 'ONLINE_SERVICE'
        ONLINE_EVENT = 'ONLINE_EVENT'
        BUNDLE = 'BUNDLE'
        COMMUNITY = 'COMMUNITY'
  • Automatic discovery and registration of the hotmart_products_list tool. server.py iterates over all modules in hotmart_mcp.tools and registers every public async function (including hotmart_products_list) via 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
  • Shared get_client() singleton used by the handler to obtain the HotmartClient instance that performs the HTTP request.
    def get_client() -> HotmartClient:
        global _client
        if _client is None:
            _client = HotmartClient()
        return _client
  • Re-exports all functions from products.py (including hotmart_products_list) so they can be discovered by the server registration loop.
    """Auto-generated: re-exports all tool functions."""
    
    from .club import *  # noqa: F401,F403
    from .coupons import *  # noqa: F401,F403
    from .negotiation import *  # noqa: F401,F403
    from .products import *  # noqa: F401,F403
    from .sales import *  # noqa: F401,F403
    from .subscriptions import *  # noqa: F401,F403
    from .tickets import *  # noqa: F401,F403
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as pagination behavior, filtering logic, or side effects. The example only shows one parameter but no return details.

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 concise (two sentences) and front-loaded with the purpose. It is efficient, though it sacrifices completeness for brevity.

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?

Despite having an output schema, the description is too sparse for a tool with 6 optional parameters. Lacks explanation of pagination, filtering, and common use cases, making it incomplete.

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 has 100% coverage, so baseline is 3. The description adds minimal value beyond the schema with an example, but does not explain parameter semantics further.

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' with a verb and resource. It is unambiguous but does not explicitly differentiate from sibling list tools like hotmart_coupons_list or hotmart_sales_history_list. The example usage adds clarity.

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 on when to use this tool versus alternatives. The description lacks context for typical use cases, prerequisites, or scenarios where it is applicable.

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