Skip to main content
Glama

hotmart_subscription_due_day_update

Updates the payment due day for a subscription. Use the subscriber code and set a new due day between 1 and 31.

Instructions

Change Due Day. Example: hotmart_subscription_due_day_update(subscriber_code='ABC123XY').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscriber_codeYesSubscriber code. Format: alphanumeric Hotmart code (ex: `H123A4B5`, not UUID, not int)
due_dayYesNovo dia de vencimento (1-31)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The async function that implements the tool logic: takes subscriber_code and due_day, sends a PATCH to /payments/api/v1/subscriptions/{subscriber_code} with the due_day in the JSON body, and returns the JSON result.
    async def hotmart_subscription_due_day_update(
        subscriber_code: str,
        due_day: int,
    ) -> str:
        """Change Due Day. Example: hotmart_subscription_due_day_update(subscriber_code='ABC123XY').
        
        Args:
            subscriber_code: Subscriber code. Format: alphanumeric Hotmart code (ex: `H123A4B5`, not UUID, not int)
            due_day: Novo dia de vencimento (1-31)"""
        endpoint = f"/payments/api/v1/subscriptions/{subscriber_code}"
        body = {}
        body["due_day"] = due_day
        result = await get_client().patch(endpoint, json=body)
        return json.dumps(result, indent=2)
  • Docstring defines the input schema: subscriber_code (str, alphanumeric Hotmart code) and due_day (int, 1-31). No formal Pydantic model; the parameters serve as the schema.
    """Change Due Day. Example: hotmart_subscription_due_day_update(subscriber_code='ABC123XY').
    
    Args:
        subscriber_code: Subscriber code. Format: alphanumeric Hotmart code (ex: `H123A4B5`, not UUID, not int)
        due_day: Novo dia de vencimento (1-31)"""
  • The function is listed in __all__ in subscriptions.py, which is re-exported via tools/__init__.py, making it available as a registered MCP tool.
    __all__ = ["hotmart_subscriptions_list", "hotmart_subscriptions_summary_list", "hotmart_subscription_transactions_list", "hotmart_subscriber_purchases_list", "hotmart_subscription_cancel", "hotmart_batch_subscriptions_cancel", "hotmart_subscription_reactivate", "hotmart_batch_subscriptions_reactivate", "hotmart_subscription_due_day_update"]
  • The get_client() helper function that provides the HotmartClient singleton used to make the PATCH request.
    def get_client() -> HotmartClient:
        global _client
        if _client is None:
            _client = HotmartClient()
        return _client
Behavior2/5

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

No annotations are present, so the description must carry the burden. It only says 'Change Due Day' without disclosing side effects, authorization needs, or constraints beyond the schema. The example is incomplete (omits due_day), which may confuse.

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?

Description is concise with one functional sentence and an example. However, the example is partially incorrect (missing due_day), reducing clarity. Still, it is appropriately front-loaded.

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 simple action and two parameters, the description is minimally adequate. But the lack of usage context and an incomplete example prevent it from being fully helpful. Output schema exists but is not leveraged.

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 baseline is 3. The description adds minimal value with an example, but the example is incomplete. It does not clarify parameter semantics beyond what the schema already provides.

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

Purpose5/5

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

Description explicitly states 'Change Due Day', which is a specific action on a subscription resource. Sibling tools cover different operations (cancel, reactivate, list), so this tool is clearly distinguished.

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, no prerequisites or exclusions. A simple two-word description provides no context for decision-making.

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