Skip to main content
Glama

Billing portal link

billing_portal_link
Read-only

Returns a short-lived link to the Stripe billing portal for the person to open in their browser, where they can change plan, update a card or buy send packs. This is the only billing tool: you never change plans or buy anything yourself. Free; changes nothing. The link expires, so get a fresh one when needed and do not store it. Requires API key scope: account.

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": "billing_portal_link"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the link's short lifetime and that it must not be stored, that calling it is free and changes no state, and that it requires API key scope 'account'. That adds auth and lifecycle context that readOnlyHint and destructiveHint alone do not convey.

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?

Three tight sentences, front-loaded with what is returned and where it is opened, followed by the routing constraint and the lifetime warning. Every sentence adds information: the destination, the delegation rule, and the expiry and scope requirement.

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?

With no input or output schema and a simple read operation, the description covers everything an agent needs: what the tool returns, where the human uses it, why the agent should not do billing work itself, how long the result lasts, and what auth it needs. No important behavior is left unstated.

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?

The tool takes zero parameters and the schema coverage is 100%, so there is nothing for the description to clarify about parameters. The baseline for a zero-parameter tool is a 4; no parameter-level detail is missing because no parameters exist.

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?

The description uses a specific verb-and-resource pair ('Returns a short-lived link to the Stripe billing portal') and spells out what the person can do at that destination: change plan, update a card, buy send packs. It also separates this tool from everything else by stating 'This is the only billing tool', so an agent can place it without opening a sibling schema.

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?

It gives explicit routing guidance rather than hints: 'you never change plans or buy anything yourself' tells the agent to delegate all billing to this tool instead of acting directly. It also gives operational guidance for repeat use: get a fresh link when needed and never store the old one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources