Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_price

Create a new price in Paddle Billing to define how to charge for products, including setting base prices, country-specific overrides, billing cycles, and tax calculations.

Instructions

This tool will create a new price in Paddle.

Prices describe how to charge for products. Always include a productId in the request to relate the price to a product.

If the quantity object is omitted, Paddle automatically sets a minimum of 1 and a maximum of 100. This means the most units that a customer can buy is 100. Set a quantity to offer a different amount.

When selecting type, choose the one that best describes the use case:

  • custom: Non-catalog item. Typically created for a specific transaction or subscription. Not returned when listing or shown in the Paddle dashboard.

  • standard: Standard item. Can be considered part of the catalog and reused across transactions and subscriptions easily.

When selecting taxMode, choose the one that best describes how the tax should be calculated for the price:

  • account_setting: Price uses the setting from the account. Default.

  • external: Price is exclusive of tax. Common in European countries.

  • internal: Price is inclusive of tax. Common in countries like the United States and Canada.

When using unitPriceOverrides:

  • Group countries based on purchasing power parity (PPP), not just currency zones

  • Create separate overrides for countries with different economic conditions even if they share the same currency (e.g., Greece and Ireland should have different price points)

  • Adjust prices relative to local economic conditions - higher in wealthy markets, lower in developing economies

  • For optimal conversion rates, set prices using local market research and willingness-to-pay data

  • Use local currencies where preferred by the customer

Example unitPriceOverrides structure: [ { "countryCodes": ["GB"], "unitPrice": { "amount": "8500", "currencyCode": "GBP" } }, { "countryCodes": ["IE"], "unitPrice": { "amount": "9500", "currencyCode": "EUR" } }, { "countryCodes": ["GR"], "unitPrice": { "amount": "6500", "currencyCode": "EUR" } }, { "countryCodes": ["IN"], "unitPrice": { "amount": "30000", "currencyCode": "INR" } }, { "countryCodes": ["CN"], "unitPrice": { "amount": "20000", "currencyCode": "CNY" } } ]

Ensure you have all the information needed before making the call. Don't fabricate, imagine, or infer details and parameter values unless explicitly asked to. If anything is ambiguous, unknown, or unclear, ask the user for clarification or details before you proceed.

If successful, the response includes a copy of the new price entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionYesInternal description for this price, not shown to customers.
typeNoType of item. Standard items are considered part of the listed catalog and are shown in the Paddle dashboard.
nameNoName of this price, shown to customers at checkout and on invoices. Typically describes how often the related product bills.
productIdYesPaddle ID for the product that this price is for, prefixed with `pro_`.
billingCycleNoHow often this price should be charged. `null` if price is non-recurring (one-time). If omitted, defaults to `null`.
trialPeriodNoTrial period for the product related to this price. The billing cycle begins once the trial period is over. `null` for no trial period. Requires `billingCycle`. If omitted, defaults to `null`.
taxModeNoHow tax is calculated for this price.
unitPriceYesBase price. This price applies to all customers, except for customers located in countries where `unitPriceOverrides` are set.
unitPriceOverridesNoList of unit price overrides. Use to override the base price with a custom price and currency for a country or group of countries.
quantityNoLimits on how many times the related product can be purchased at this price. Useful for discount campaigns. If omitted, defaults to 1-100.
customDataNoAny structured custom key-value data needed outside of Paddle's standard fields. Occasionally used by third-parties.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changedv1.0.0
    • changedInput schema / properties / billingCycle / description
      Previous value: -"For subscription prices, defines the recurring billing period"New value: +"How often this price should be charged. `null` if price is non-recurring (one-time). If omitted, defaults to `null`."
    • changedInput schema / properties / billingCycle / properties / frequency / description
      Previous value: -"How many intervals make up one billing cycle (e.g., 2 weeks, 3 months)"New value: +"Amount of time."
    • changedInput schema / properties / billingCycle / properties / interval / description
      Previous value: -"The billing period unit (day, week, month, or year)"New value: +"Unit of time."
    • changedInput schema / properties / customData / description
      Previous value: -"A JSON object of custom metadata. Limited to 50 keys, with key names up to 40 characters"New value: +"Any structured custom key-value data needed outside of Paddle's standard fields. Occasionally used by third-parties."
    • changedInput schema / properties / description / description
      Previous value: -"A description of this price that will be displayed to customers"New value: +"Internal description for this price, not shown to customers."
    • changedInput schema / properties / name / description
      Previous value: -"The name of the price"New value: +"Name of this price, shown to customers at checkout and on invoices. Typically describes how often the related product bills."
    • changedInput schema / properties / productId / description
      Previous value: -"The ID of the product this price is for"New value: +"Paddle ID for the product that this price is for, prefixed with `pro_`."
    • changedInput schema / properties / quantity / description
      Previous value: -"Quantity limits for this price"New value: +"Limits on how many times the related product can be purchased at this price. Useful for discount campaigns. If omitted, defaults to 1-100."
    • changedInput schema / properties / quantity / properties / maximum / description
      Previous value: -"The maximum quantity that can be purchased. Must be greater than minimum if specified"New value: +"Maximum quantity of the product related to this price that can be bought. Required if `minimum` set. Must be greater than or equal to the `minimum` value."
    • changedInput schema / properties / quantity / properties / minimum / description
      Previous value: -"The minimum quantity that can be purchased. Must be at least 1 if specified"New value: +"Minimum quantity of the product related to this price that can be bought. Required if `maximum` set."
    • addedInput schema / properties / quantity / required
      Added value: +[
+  "minimum",
+  "maximum"
+]
    • addedInput schema / properties / taxMode
      Added value: +{
+  "description": "How tax is calculated for this price.",
+  "enum": [
+    "account_setting",
+    "external",
+    "internal"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / trialPeriod / description
      Previous value: -"For subscription prices with a trial, defines the trial period duration"New value: +"Trial period for the product related to this price. The billing cycle begins once the trial period is over. `null` for no trial period. Requires `billingCycle`. If omitted, defaults to `null`."
    • changedInput schema / properties / trialPeriod / properties / frequency / description
      Previous value: -"How many intervals make up the trial period (e.g., 14 days, 1 month)"New value: +"Amount of time."
    • changedInput schema / properties / trialPeriod / properties / interval / description
      Previous value: -"The trial period unit (day, week, month, or year)"New value: +"Unit of time."
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Type of item. Standard items are considered part of the listed catalog and are shown in the Paddle dashboard.",
+  "enum": [
+    "custom",
+    "standard"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / unitPrice / description
      Previous value: -"The base price details"New value: +"Base price. This price applies to all customers, except for customers located in countries where `unitPriceOverrides` are set."
    • changedInput schema / properties / unitPrice / properties / amount / description
      Previous value: -"The price amount in the smallest currency unit (e.g., cents). Must be a positive integer represented as a string"New value: +"Amount in the lowest denomination for the currency, e.g. 10 USD = 1000 (cents). Although represented as a string, this value must be a valid integer."
    • changedInput schema / properties / unitPrice / properties / currencyCode / description
      Previous value: -"The three-letter ISO 4217 currency code (e.g., USD, EUR, GBP)"New value: +"Supported three-letter ISO 4217 currency code."
    • addedInput schema / properties / unitPrice / properties / currencyCode / enum
      Added value: +[
+  "USD",
+  "EUR",
+  "GBP",
+  "JPY",
+  "AUD",
+  "CAD",
+  "CHF",
+  "HKD",
+  "SGD",
+  "SEK",
+  "ARS",
+  "BRL",
+  "CNY",
+  "COP",
+  "CZK",
+  "DKK",
+  "HUF",
+  "ILS",
+  "INR",
+  "KRW",
+  "MXN",
+  "NOK",
+  "NZD",
+  "PLN",
+  "RUB",
+  "THB",
+  "TRY",
+  "TWD",
+  "UAH",
+  "VND",
+  "ZAR"
+]
    • changedInput schema / properties / unitPriceOverrides / description
      Previous value: -"Country-specific price overrides. Used for regional pricing"New value: +"List of unit price overrides. Use to override the base price with a custom price and currency for a country or group of countries."
    • changedInput schema / properties / unitPriceOverrides / items / properties / countryCodes / description
      Previous value: -"List of two-letter ISO 3166-1 alpha-2 country codes where this override applies"New value: +"Supported two-letter ISO 3166-1 alpha-2 country code. Customers located in the listed countries are charged the override price."
    • addedInput schema / properties / unitPriceOverrides / items / properties / countryCodes / items / enum
      Added value: +[
+  "AD",
+  "AE",
+  "AG",
+  "AI",
+  "AL",
+  "AM",
+  "AO",
+  "AR",
+  "AS",
+  "AT",
+  "AU",
+  "AW",
+  "AX",
+  "AZ",
+  "BA",
+  "BB",
+  "BD",
+  "BE",
+  "BF",
+  "BG",
+  "BH",
+  "BI",
+  "BJ",
+  "BL",
+  "BM",
+  "BN",
+  "BO",
+  "BQ",
+  "BR",
+  "BS",
+  "BT",
+  "BV",
+  "BW",
+  "BZ",
+  "CA",
+  "CC",
+  "CG",
+  "CH",
+  "CI",
+  "CK",
+  "CL",
+  "CM",
+  "CN",
+  "CO",
+  "CR",
+  "CV",
+  "CW",
+  "CX",
+  "CY",
+  "CZ",
+  "DE",
+  "DJ",
+  "DK",
+  "DM",
+  "DO",
+  "DZ",
+  "EC",
+  "EE",
+  "EG",
+  "EH",
+  "ER",
+  "ES",
+  "ET",
+  "FI",
+  "FJ",
+  "FK",
+  "FM",
+  "FO",
+  "FR",
+  "GA",
+  "GB",
+  "GD",
+  "GE",
+  "GF",
+  "GG",
+  "GH",
+  "GI",
+  "GL",
+  "GM",
+  "GN",
+  "GP",
+  "GQ",
+  "GR",
+  "GS",
+  "GT",
+  "GU",
+  "GW",
+  "GY",
+  "HK",
+  "HM",
+  "HN",
+  "HR",
+  "HU",
+  "ID",
+  "IE",
+  "IL",
+  "IM",
+  "IN",
+  "IO",
+  "IQ",
+  "IS",
+  "IT",
+  "JE",
+  "JM",
+  "JO",
+  "JP",
+  "KE",
+  "KG",
+  "KH",
+  "KI",
+  "KM",
+  "KN",
+  "KR",
+  "KW",
+  "KY",
+  "KZ",
+  "LA",
+  "LB",
+  "LC",
+  "LI",
+  "LK",
+  "LR",
+  "LS",
+  "LT",
+  "LU",
+  "LV",
+  "MA",
+  "MC",
+  "MD",
+  "ME",
+  "MF",
+  "MG",
+  "MH",
+  "MK",
+  "MN",
+  "MO",
+  "MP",
+  "MQ",
+  "MR",
+  "MS",
+  "MT",
+  "MU",
+  "MV",
+  "MW",
+  "MX",
+  "MY",
+  "MZ",
+  "NA",
+  "NC",
+  "NE",
+  "NF",
+  "NG",
+  "NL",
+  "NO",
+  "NP",
+  "NR",
+  "NU",
+  "NZ",
+  "OM",
+  "PA",
+  "PE",
+  "PF",
+  "PG",
+  "PH",
+  "PK",
+  "PL",
+  "PM",
+  "PN",
+  "PR",
+  "PS",
+  "PT",
+  "PW",
+  "PY",
+  "QA",
+  "RE",
+  "RO",
+  "RS",
+  "RW",
+  "SA",
+  "SB",
+  "SC",
+  "SE",
+  "SG",
+  "SH",
+  "SI",
+  "SJ",
+  "SK",
+  "SL",
+  "SM",
+  "SN",
+  "SR",
+  "ST",
+  "SV",
+  "SX",
+  "SZ",
+  "TC",
+  "TD",
+  "TF",
+  "TG",
+  "TH",
+  "TJ",
+  "TK",
+  "TL",
+  "TM",
+  "TN",
+  "TO",
+  "TR",
+  "TT",
+  "TV",
+  "TW",
+  "TZ",
+  "UA",
+  "UG",
+  "UM",
+  "US",
+  "UY",
+  "UZ",
+  "VA",
+  "VC",
+  "VG",
+  "VI",
+  "VN",
+  "VU",
+  "WF",
+  "WS",
+  "XK",
+  "YT",
+  "ZA",
+  "ZM"
+]
    • changedInput schema / properties / unitPriceOverrides / items / properties / unitPrice / description
      Previous value: -"The override price details"New value: +"Override price. This price applies to customers located in the countries for this unit price override."
    • changedInput schema / properties / unitPriceOverrides / items / properties / unitPrice / properties / amount / description
      Previous value: -"The override price amount in the smallest currency unit. Must be a positive integer represented as a string"New value: +"Amount in the lowest denomination for the currency, e.g. 10 USD = 1000 (cents). Although represented as a string, this value must be a valid integer."
    • changedInput schema / properties / unitPriceOverrides / items / properties / unitPrice / properties / currencyCode / description
      Previous value: -"The three-letter ISO 4217 currency code (e.g., USD, EUR, GBP)"New value: +"Supported three-letter ISO 4217 currency code."
    • addedInput schema / properties / unitPriceOverrides / items / properties / unitPrice / properties / currencyCode / enum
      Added value: +[
+  "USD",
+  "EUR",
+  "GBP",
+  "JPY",
+  "AUD",
+  "CAD",
+  "CHF",
+  "HKD",
+  "SGD",
+  "SEK",
+  "ARS",
+  "BRL",
+  "CNY",
+  "COP",
+  "CZK",
+  "DKK",
+  "HUF",
+  "ILS",
+  "INR",
+  "KRW",
+  "MXN",
+  "NOK",
+  "NZD",
+  "PLN",
+  "RUB",
+  "THB",
+  "TRY",
+  "TWD",
+  "UAH",
+  "VND",
+  "ZAR"
+]
    • changedInput schema / required
      Previous value: -[
-  "productId",
-  "description",
-  "unitPrice"
-]New value: +[
+  "description",
+  "productId",
+  "unitPrice"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds valuable behavioral context beyond this. It explains default behaviors ('If the quantity object is omitted, Paddle automatically sets a minimum of 1 and a maximum of 100'), provides implementation guidance for unitPriceOverrides, and specifies the response format ('If successful, the response includes a copy of the new price entity'). This goes beyond what annotations provide without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is comprehensive but lengthy, with multiple sections that could be more efficiently organized. While all content is relevant, the extensive example and implementation advice for unitPriceOverrides (7 bullet points plus a detailed example) makes it less concise than ideal. The core purpose is clear upfront, but the structure includes substantial implementation guidance that might be better placed elsewhere.

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?

Given the tool's complexity (11 parameters, nested objects, no output schema), the description provides excellent contextual completeness. It covers required parameters, explains parameter implications, provides implementation guidance, specifies response format, and includes warnings about data requirements. This adequately compensates for the lack of output schema and provides comprehensive guidance for this creation tool.

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?

With 100% schema description coverage, the baseline is 3. The description adds significant value by explaining the practical implications of parameter choices: it clarifies when to use 'custom' vs 'standard' types, explains taxMode options with regional examples, provides detailed guidance on unitPriceOverrides implementation strategies, and explains the default behavior when quantity is omitted. This adds meaningful context beyond the schema's technical definitions.

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 explicitly states 'create a new price in Paddle' and explains that 'Prices describe how to charge for products.' This provides a specific verb ('create') and resource ('price'), clearly distinguishing it from sibling tools like 'get_price' or 'list_prices' which are read operations rather than creation tools.

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?

The description provides clear context about when to use this tool: 'Always include a productId in the request to relate the price to a product.' It also offers guidance on parameter selection (e.g., 'When selecting type, choose the one that best describes the use case'). However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among siblings.

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