Skip to main content
Glama
Sign In
hotmart-mcp

hotmart-mcp

by thaleslaray
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hotmart_module_pages_list

Retrieve pages from a specific module in your Hotmart members area. Requires module ID and subdomain from your club URL.

Instructions

Get Pages. Example: hotmart_module_pages_list(module_id='…'). Requires module_id from hotmart_modules_list first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "module_id": "<module_id>",
      "subdomain": "<subdomain>"
    },
    "name": "hotmart_module_pages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
module_idYesModule ID
subdomainYesMembers area subdomain (the slug from `hotmart.com/club/<slug>` URL)
selectNoCustom field selection in response

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. However, it only states 'Get Pages' which implies a read operation, but does not confirm read-only behavior, mention side effects, pagination, or rate limits. The description fails to add transparency beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence plus an example), which is concise but at the expense of completeness. It front-loads the purpose but is too minimal to fully inform the agent.

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 tool has 3 parameters (2 required) and an output schema, the description is insufficient. It does not explain what 'pages' are, how subdomain is used, or how results are structured. The output schema exists but the description should still provide context about the tool's function in the module workflow.

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 input schema already describes all parameters. The description adds only an example using module_id, which is helpful but does not provide additional meaning for subdomain or select. It adds marginal value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get Pages' is vague and does not specify what kind of pages (e.g., module content pages). The example provides some context but lacks clarity on the resource type. It does not differentiate from sibling list tools like hotmart_modules_list.

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

Usage Guidelines4/5

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

The description explicitly states a prerequisite: 'Requires module_id from hotmart_modules_list first.' This gives clear sequencing guidance, though it does not specify when not to use the tool or suggest alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools