Skip to main content
Glama

extend_customer_trial

Extend a customer's Stripe subscription trial by 1-30 days, with dry-run preview and idempotency to prevent duplicate extends, for internal support use.

Instructions

Extend your account's Stripe subscription trial by 1-30 days (POST /v1/tier2/trial/extend). Founder-operations only (an internal support tool; general accounts get 403). Trial extension directly affects revenue, so there is no plan to open it up. Cumulative cap of 60 days (aggregated from the last 30 days of audit logs); 409 unless status='trialing'. dryRun must be passed explicitly (guards against accidental mutation via an implicit false); when dryRun=false, idempotencyKey is also required (16-128 alphanumeric plus '_-'). Re-calling with the same key returns the cached result via the tier2_idempotency table (structurally preventing retry double-extends). dryRun=true previews previousTrialEnd / newTrialEnd / the cumulative total only (no Stripe call); dryRun=false performs the actual Stripe mutation plus the accounts_subscription sync update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunYesMust be passed explicitly. true = preview only; false = actual trial extension + Stripe mutation
reasonYesReason for the extension (recorded in the audit log; required, 200 chars max)
approvalIdNoApproval id granted via request_approval (apr_ + 32 hex; create with action 'extend_customer_trial'). Server-side verification + atomic consumption on a fresh execution (1 approval = 1 execution chain; retries with the same idempotencyKey do not re-consume). dryRun only verifies
extendDaysYesDays to extend (1-30, cumulative cap 60 days)
idempotencyKeyNoRequired when dryRun=false. 16-128 chars alphanumeric plus '_-'; re-calls with the same key return the cached result
targetAccountIdYesTarget account id (your own account only for now; specifying another user gets 403)
Behavior5/5

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

With no annotations provided, the description carries full burden. It details the dryRun behavior (preview vs mutation), idempotency key caching, cumulative cap, Stripe mutation side effects, and approvalId atomic consumption. Comprehensive disclosure.

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?

Dense single paragraph with all essential information front-loaded. Every sentence adds value. Slightly long but appropriate for the complexity; could be broken into bullet points for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, yet the description explains return values for dryRun (preview of dates and cumulative total) and the actual mutation effects. Covers error conditions (403, 409) and status checks. Complete for a sensitive financial tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds critical context beyond schema: dryRun must be explicit, idempotencyKey required when dryRun=false, cumulative cap explanation, and atomic approvalId consumption. Enriches all parameters.

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?

Clearly states the verb 'extend' and the resource 'Stripe subscription trial' with a specific range (1-30 days). Includes the HTTP endpoint and distinguishes itself from sibling tools by noting it's an internal support tool for founder-operations only.

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

Usage Guidelines5/5

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

Explicitly states when to use (founder-operations, status='trialing'), when not to use (general accounts get 403), and limitations (cumulative cap of 60 days). Provides clear context for usage.

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/argosvix/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server