Skip to main content
Glama

Get a link to manage billing

get_billing_portal_link

Returns a link to the Stripe billing portal, where the user changes or cancels the plan, updates the card, and downloads invoices.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, and the description correctly frames the tool as producing a Stripe-hosted session link rather than mutating data itself. It does not disclose practical constraints an agent would benefit from, such as whether the link expires, is single-use, or requires an existing Stripe customer/subscription before it will succeed. No contradiction with the non-read-only annotation, since the portal does enable downstream changes.

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?

A single sentence front-loads the return value and then supplies the purpose in a compact relative clause. Every element (Stripe, portal, four user actions) adds information; nothing is redundant.

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?

For a zero-parameter tool with no output schema, the definition supplies enough to call it correctly: what comes back and what the recipient can do with it. The only meaningful omission is failure behavior — what is returned or raised when the account has no billing profile or subscription to manage.

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, so the schema imposes no documentation burden and the description has nothing parameter-related to compensate for. Baseline for a no-parameter tool applies.

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 names a specific verb and resource ('Returns a link to the Stripe billing portal') and enumerates the concrete tasks the portal enables (change/cancel plan, update card, download invoices). This makes the tool's function unmistakable, though it does not explicitly contrast itself with checkout-creation or plan-listing siblings.

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?

By listing the user actions the portal supports (changing or cancelling a plan, updating a card, downloading invoices), it makes the use case clear: self-service subscription management rather than initiating a new purchase. It stops short of naming alternatives or stating exclusions, such as when to use a checkout-creating sibling instead.

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