Mubert Music MCP

Create a checkout link

create_checkout_link

Create a Stripe Checkout link for a plan.

Returns a URL. It does not charge anyone — the user has to open it and enter payment details themselves. Show them the plan, its price and what it changes before handing the link over.

Creating a link for an email that already has a company attaches the subscription to that existing company.

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": {
      "stripe_price_id": "<stripe_price_id>",
      "email": "<email>"
    },
    "name": "create_checkout_link"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Billing email. The company is found or created from it.
`coupon_id`	No
`company_name`	No
`redirect_url`	No	Where Stripe sends the user after paying.
`stripe_price_id`	Yes	From list_plans.
`redirect_url_cancel`	No

Output Schema

Name	Required	Description	Default
`next_step`	Yes
`session_id`	No
`checkout_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the key behaviors an agent would otherwise get wrong: the call itself moves no money, a URL is returned for the user to complete payment, and passing an email tied to an existing company attaches the subscription to that company. That last detail is a real side-effect disclosure no annotation covers.

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?

Front-loaded with the verb, resource and return value in the first two lines, and each following sentence carries information (no-charge, existing-company attachment). Slightly instruction-flavored ('Show them the plan...'), which is useful but reads more like prompt text than tool documentation.

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?

An output schema exists, so the description needn't explain the response shape, and it covers the critical non-obvious semantics (no immediate charge, existing-company linkage). Remaining gaps are the undocumented optional parameters (coupon_id, company_name, redirect_url_cancel) and failure/expiry behavior for the generated link.

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?

Schema coverage is 50%, and the description only reinforces what the schema already says for email ('company is found or created from it') and stripe_price_id ('from list_plans'). coupon_id, company_name and redirect_url_cancel get no added meaning anywhere, so the description does not compensate for the coverage gap.

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?

Specific verb + resource: 'Create a Stripe Checkout link for a plan', plus the concrete return ('Returns a URL'). It is distinguishable from siblings like open_billing_portal, provision_customer and list_plans — this is the link-generation step, and the description makes that role obvious without opening a schema.

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?

Gives real usage context: it does not charge anyone, the user must open the link and pay, and the agent should present the plan, price and change set first. It does not name the adjacent alternatives (open_billing_portal, provision_customer) or state exclusions, so it falls short of a 5.

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

All Mubert Music MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?