Skip to main content
Glama

create_payment_link

Create a unique payment link to receive payments by entering recipient name, payment purpose, and customer email or mobile number. Optionally set a fixed amount.

Instructions

Create a new payment link for receiving payments.

This operation generates a unique payment link that can be shared with customers
for accepting payments. The link can be customized with recipient details,
purpose, customer details and amount.

Required Parameters:
    recipient_name (str): Name of the person or entity receiving the payment
    purpose (str): Description or reason for the payment
    customer_email (str): Email address of the customer
    customer_mobile (str): Mobile number of the customer
    Either customer_email or customer_mobile must be provided if else please ask from the user

Optional Parameters:
    amount (float): Fixed amount for the payment

Note:
    - Amount can be left optional for customer to decide
    - Generated link will be valid according to system's expiry settings
    - Please ask all the required fields from the user don't assume any fields

IMPORTANT NOTE:
    - if user is not providing customer_email or customer_mobile, please ask for the same don't call any tool before asking for the same
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recipient_nameYes
purposeYes
customer_emailNo
customer_mobileNo
amountNo
Behavior4/5

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

No annotations are provided, so the description must disclose behavior. It mentions link expiry, optional amount, and conditional requirement of email/mobile. It does not detail error handling or idempotency, but for a creation tool it provides adequate transparency.

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?

The description is well-structured with an intro, required/optional lists, and notes. The front-loaded sentence clearly states purpose. Repetition in 'IMPORTANT NOTE' reduces conciseness slightly.

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?

The description covers parameter semantics well but does not explain the return value or output structure. Given no output schema, this omission makes the tool less complete for the agent to understand what to expect.

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?

Schema coverage is 0%, so the description compensates by listing all parameters with usage details. It adds meaning beyond schema by specifying conditional requirements and optionality. However, there is a slight inconsistency: description says amount is float but schema defines it as string.

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 clearly states the verb 'Create' and the resource 'payment link for receiving payments'. It distinguishes from sibling tools 'fetch_payment_links' and 'fetch_transactions_for_link' which are retrieval operations.

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

Usage Guidelines5/5

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

The description explicitly instructs the agent to ask for all required fields from the user before calling the tool, and provides conditional requirements for customer_email or customer_mobile. It also notes not to call the tool before obtaining these fields.

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/santosh-chourasiya/payment-mcp-server'

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