Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ

create_business

Create a new business entity for a customer in Paddle to manage business information when working with companies rather than individuals.

Instructions

This tool will create a new business for a customer in Paddle.

Business entities hold business information for a customer when working with a business rather than an individual. Customers do not need to have a business to make a purchase, but should if working with a business.

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 business entity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesPaddle ID of the customer.
nameYesFull name.
companyNumberNoCompany number for this business.
taxIdentifierNoTax or VAT Number for this business.
contactsNoList of contacts related to this business, typically used for sending invoices.
customDataNoAny structured custom key-value data needed outside of Paddle's standard fields. Occasionally used by third-parties.

Implementation Reference

  • The handler function that executes the create_business tool by calling paddle.businesses.create with the provided customerId and business data.
    export const createBusiness = async (paddle: Paddle, params: z.infer<typeof Parameters.createBusinessParameters>) => {
      try {
        const { customerId, ...updateData } = params;
        const business = await paddle.businesses.create(customerId, updateData);
        return business;
      } catch (error) {
        return error;
      }
    };
  • src/tools.ts:336-347 (registration)
    Tool registration object defining the 'create_business' method, its name, description prompt, parameters schema, and required actions for the MCP tool.
    {
      method: "create_business",
      name: "Create a business for a customer",
      description: prompts.createBusinessPrompt,
      parameters: params.createBusinessParameters,
      actions: {
        businesses: {
          write: true,
          create: true,
        },
      },
    },
  • src/api.ts:38-38 (registration)
    Maps the CREATE_BUSINESS constant to the createBusiness handler function in the PaddleAPI toolMap for execution.
    [TOOL_METHODS.CREATE_BUSINESS]: funcs.createBusiness,
  • src/constants.ts:30-30 (registration)
    Defines the TOOL_METHODS.CREATE_BUSINESS constant string used in tool registrations and mappings.
    CREATE_BUSINESS: "create_business",
  • Prompt providing guidance and description for the create_business tool usage.
    export const createBusinessPrompt = `
    This tool will create a new business for a customer in Paddle.
    
    Business entities hold business information for a customer when working with a business rather than an individual. Customers do not need to have a business to make a purchase, but should if working with a business.
    
    ${additionalDetailsWarning}
    
    If successful, the response includes a copy of the new business entity.
    `;
Behavior3/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, confirming this is a non-destructive write operation. The description adds that it creates a new entity and includes a copy in the response if successful, which provides useful behavioral context beyond annotations. However, it doesn't detail error conditions, rate limits, or authentication requirements, leaving gaps in transparency.

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 front-loaded with the tool's purpose but includes verbose warnings about not fabricating details and asking for clarification, which are generic and could be condensed. It's moderately structured but has some redundancy, reducing efficiency.

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

Completeness3/5

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

Given 6 parameters with 100% schema coverage, annotations covering safety, and no output schema, the description is adequate but not comprehensive. It explains the tool's purpose and success response but lacks details on failure modes, side effects, or integration with sibling tools, leaving room for improvement in context.

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 description coverage is 100%, so parameters are well-documented in the schema. The description doesn't add any specific parameter semantics beyond implying that all information should be gathered before calling. This meets the baseline of 3 since the schema carries the burden, but no extra value is provided.

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 clearly states the tool creates a new business entity for a customer in Paddle and explains what business entities are. It distinguishes from individual customers but doesn't explicitly differentiate from sibling tools like create_customer or get_business beyond the name. The purpose is specific but lacks direct sibling comparison.

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 provides implied guidance: use when working with a business rather than an individual, and customers don't need a business to purchase. It warns against fabricating details and advises asking for clarification if ambiguous. However, it doesn't explicitly state when to use this vs. alternatives like create_customer or get_business, nor does it mention prerequisites beyond having information ready.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaddleHQ/paddle-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server