Skip to main content
Glama

Open the billing portal

billing_portal

Create a Stripe billing portal URL. Workspace owners only; return the URL to the user to manage their subscription in their browser.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "billing_portal"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-destructive, non-idempotent, open-world behavior, and the description adds genuinely new facts: the call requires workspace-owner authorization and the output is a URL meant for the user's browser, not for server-side consumption. It does not mention URL expiry, single-use semantics, or what happens when a caller lacks owner rights, which are the remaining behavioral gaps.

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?

Two short sentences with no filler, and the owner restriction is placed early where an agent will see it. The trailing "in their browser" clause is slightly redundant with "return the URL to the user" but not wasteful.

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 one-parameter tool with no output schema, the definition covers the essentials: authorization level, the artifact produced, and what the agent should do with it. Missing details such as portal session lifetime or failure modes for non-owners keep it short of full completeness.

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?

There is a single parameter with 100% schema description coverage, which already explains that workspace_id comes from whoami, so the baseline is 3. The description adds no extra meaning about the identifier beyond the schema.

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?

"Create a Stripe billing portal URL" gives a concrete verb plus a named resource, and adds the audience constraint "Workspace owners only" plus the intended outcome (subscription management). It does not name a sibling such as billing_checkout or get_billing to differentiate, so an agent must infer the split from the resource naming alone.

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

Usage Guidelines3/5

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

The description supplies meaningful usage context: this is for owners to manage their subscription in a browser, and the URL should be handed back to the user rather than acted on. It stops short of stating when to prefer a direct checkout flow (billing_checkout) or read-only billing info (get_billing), so tool selection between billing siblings remains implied.

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