Skip to main content
Glama
MCP Dokploy Online
by igoruam

stripe-createCustomerPortalSession

Creates a Stripe customer portal session so users can manage subscriptions, payment methods, and invoices.

Instructions

POST /stripe.createCustomerPortalSession

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": "stripe-createCustomerPortalSession"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations supply only openWorldHint=true; the description adds nothing about what the call returns (a portal URL?), whether it acts on the caller's own customer, or any auth/rate-limit behavior. The POST verb hints at mutation/creation, which is consistent with a session-issuing call but not elaborated. Nothing contradicts the annotations, so this is a gap rather than a contradiction.

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?

It is short, but this is under-specification rather than concision—a single URL-like fragment with no front-loaded statement of purpose. No sentence earns additional value because none carries information beyond the name.

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

Completeness1/5

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

With no output schema and thin annotations, the description carries the full burden and delivers nothing: no return value, no side effects, no indication of which customer the session is for. An agent cannot tell what happens after invocation or what to do with the result.

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 per the baseline there is nothing for the description to disambiguate. It could still note that the customer is implied by the authenticated context, but the empty schema means no semantic loss.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is an endpoint restatement: 'POST /stripe.createCustomerPortalSession' only echoes the tool name plus an HTTP verb. An agent can infer the resource (a Stripe customer portal session) and that it is a creation call, but nothing states what a portal session is or what it enables, and no sibling (e.g. stripe-createCheckoutSession) is differentiated.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as stripe-createCheckoutSession or stripe-getBillingStatus. The agent must guess from the name alone.

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

Deploy Server

Other Tools