Skip to main content
Glama

hotmart_student_progress_get

Retrieve a student's progress in a Hotmart members area by providing the user ID and subdomain. Customize field selection with optional parameters.

Instructions

Get Student Progress. Example: hotmart_student_progress_get(user_id='…').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesID do aluno
subdomainYesMembers area subdomain (the slug from `hotmart.com/club/<slug>` URL)
selectNoCustom field selection in response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the hotmart_student_progress_get tool. It is an async function that takes user_id, subdomain, and optional select params, calls GET /club/api/v1/users/{user_id}/lessons endpoint via the shared API client, and returns JSON-formatted result.
    async def hotmart_student_progress_get(
        user_id: str,
        subdomain: str,
        select: Optional[str] = None,
    ) -> str:
        """Get Student Progress. Example: hotmart_student_progress_get(user_id='…').
        
        Args:
            user_id: ID do aluno
            subdomain: Members area subdomain (the slug from `hotmart.com/club/<slug>` URL)
            select: Custom field selection in response"""
        endpoint = f"/club/api/v1/users/{user_id}/lessons"
        params = {}
        if subdomain is not None:
            params["subdomain"] = subdomain
        if select is not None:
            params["select"] = select
        result = await get_client().get(endpoint, params=params)
        return json.dumps(result, indent=2)
  • LessonProgress Pydantic model used to type the response from the student progress endpoint. Contains fields like page_id, page_name, module_name, is_completed, completed_date.
    class LessonProgress(BaseModel):
        page_id: str | None = Field(None, description='ID da página/aula')
        page_name: str | None = Field(None, description='Nome da página/aula')
        module_name: str | None = Field(None, description='Nome do módulo')
        is_module_extra: bool | None = Field(None, description='Se o módulo é extra')
        is_completed: bool | None = Field(None, description='Se a aula foi concluída')
        completed_date: int | None = Field(
            None, description='Data de conclusão (timestamp ms)'
        )
  • Automatic discovery and registration via _discover_and_register_tools(). It imports all modules under hotmart_mcp.tools (including club.py), finds all async functions that don't start with '_', and registers them as FastMCP tools via mcp.tool()(obj).
    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
  • get_client() shared helper that provides a singleton HotmartClient instance used by the tool handler to make API calls.
    def get_client() -> HotmartClient:
        global _client
        if _client is None:
            _client = HotmartClient()
        return _client
  • The __all__ export list in club.py that includes 'hotmart_student_progress_get' so it is re-exported via tools/__init__.py.
    __all__ = ["hotmart_modules_list", "hotmart_module_pages_list", "hotmart_students_list", "hotmart_student_progress_get"]
Behavior2/5

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

Annotations are missing, so the description must carry the full burden. It only states the basic function without disclosing side effects, authentication needs, or output structure (though an output schema exists but is not referenced).

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 front-loaded with the most critical info (action and example). It earns its place but could benefit from a bit more detail without becoming verbose.

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 and well-defined parameters, the description is too minimal. It does not explain what 'progress' entails, how the response is structured, or any limitations. For a tool with many siblings, this is insufficient.

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 the baseline is 3. The description adds minimal value beyond the schema, only providing an example call that illustrates the 'user_id' parameter. No additional semantic context is given.

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 'Get Student Progress' with an example call, indicating the action and resource. However, it does not differentiate from sibling tools like hotmart_students_list or hotmart_students_overview_app, which limits clarity in a crowded context.

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, such as other student-related tools. The description lacks context about prerequisites or intended use cases.

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