Skip to main content
Glama
Sign In
hotmart-mcp

hotmart-mcp

by thaleslaray
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

hotmart_product_plans_list

List all plans for a Hotmart product using its product ID, with options for pagination and field selection.

Instructions

Get Product Plans. Example: hotmart_product_plans_list(product_id=12345, max_results=10).

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": {
      "product_id": "<product_id>"
    },
    "name": "hotmart_product_plans_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct ID
max_resultsNoMax results per page
page_tokenNoPagination token for the next page
id_NoID do plano
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, and the description does not disclose behavioral traits such as read-only nature, pagination behavior, or rate limits. The description is insufficient to compensate for missing annotations.

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 extremely concise with one sentence and an example. No unnecessary words, and the example provides quick understanding.

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 5 parameters and no annotations, the description is incomplete. It does not explain pagination, filtering by plan ID, or the custom select feature. The presence of an output schema does not compensate for missing behavioral context.

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?

The input schema has 100% coverage, so the schema already documents parameters. The description adds minimal value by showing an example with product_id and max_results, but other parameters (page_token, id_, select) are not addressed.

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 states 'Get Product Plans' with an example, providing a clear verb and resource. However, it does not differentiate from siblings like hotmart_product_offers_list, which could also deal with product-related data.

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 given on when to use this tool versus alternatives. The description lacks when-to-use, when-not-to-use, or mentions of related tools.

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