Skip to main content
Glama

Get a checkout link for credits or a plan

autoshort_get_buy_credits_url
Read-onlyIdempotent

Returns a checkout link to buy a credit pack or start a plan for a human to open and pay, then verify the credit balance afterward.

Instructions

A checkout link to buy credits (pack) or start a plan (plan, 3-day trial) on Whop — for the human to open and pay once. No email or personal data is in the link. Packs: MICRO, STARTER, VALUE, MEGA. For a new customer, EPISODE is the first episode pack: 350 credits, enough for one 12-second Character Studio drama episode. AI-generated video. Credits do not expire while your account is active. One-time purchase, no renewal. First purchase 50% off the regular $6.99. A new account's first video can be free, in the web app or through autoshort_render_draft when the account has no credits (one watermarked video per person, a daily cap of 20 shared by all accounts; not available through direct REST calls with an API key), then EPISODE at $3.49 on a first purchase is the next step. After they pay, poll autoshort_get_credit_balance. If the owner enabled auto-recharge, use autoshort_buy_credits instead (no link). Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autoshort_get_buy_credits_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
packNoOne-time credit pack.
planNoMonthly plan (instead of a pack).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered; the description adds real context beyond that — no email or personal data is embedded in the link, it is a one-time purchase with no renewal, and credits do not expire. The 'Free.' fragment at the end is ambiguous and adds no usable behavioral information.

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

Conciseness2/5

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

For a zero-required-parameter link getter, the description sprawls into pricing ($6.99, $3.49, 50% off), watermark policy, and a daily cap of 20 shared by all accounts — promotional copy that does not help an agent select or invoke the tool. The useful purpose sentence is front-loaded, but the middle is unfocused and ends on a dangling 'Free.'

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

Completeness4/5

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

With no output schema and only two optional enum parameters, the agent needs little, and the description covers the important gaps: that a human must complete payment, and that the balance should be re-checked afterward. It is over-supplied with marketing detail rather than under-supplied, so completeness is not the deficiency.

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

Parameters4/5

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

Schema coverage is 100% with both enums documented, so the baseline is 3; the description earns more by giving meaning the schema does not — plan carries a 3-day trial, EPISODE is the 350-credit first-episode pack sized for one 12-second episode, and first purchase is discounted. It never states what happens if both pack and plan are supplied or omitted.

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 opening sentence states a specific deliverable: a checkout link for buying credits (pack) or starting a plan, explicitly framed as 'for the human to open and pay once,' which makes clear the agent does not itself transact. The distinction from autoshort_buy_credits appears only in the closing sentences, so the divergence from the most similar sibling is not front-loaded.

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?

Genuine routing guidance is present: use autoshort_buy_credits instead when auto-recharge is enabled, poll autoshort_get_credit_balance after payment, and use autoshort_render_draft for a free first video. It lacks an explicit statement of when neither pack nor plan is appropriate, and the guidance is scattered across the tail rather than stated as rules.

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