Skip to main content
Glama

xero_payments_list

List payments from Xero with pagination. Optionally filter by status to view authorized or deleted payments.

Instructions

List payments in Xero with pagination. Optionally filter by status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based, default: 1). Each page returns up to 100 payments.
StatusNoFilter by payment status

Implementation Reference

  • Handler case for 'xero_payments_list' inside handlePaymentTool. Extracts optional 'page' and 'Status' args, builds query params, calls GET 'Payments' endpoint, and returns the JSON response.
    case "xero_payments_list": {
      const { page, Status } = args as {
        page?: number;
        Status?: string;
      };
      const params: Record<string, string> = {};
      if (page !== undefined) params.page = String(page);
      if (Status) params.where = `Status=="${Status}"`;
    
      const response = await client.get("Payments", params);
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
      };
  • Schema definition for 'xero_payments_list' tool. Defines inputSchema with optional 'page' (number) and 'Status' (string enum: AUTHORISED, DELETED) properties.
    name: "xero_payments_list",
    description:
      "List payments in Xero with pagination. Optionally filter by status.",
    inputSchema: {
      type: "object",
      properties: {
        page: {
          type: "number",
          description: "Page number (1-based, default: 1). Each page returns up to 100 payments.",
        },
        Status: {
          type: "string",
          enum: ["AUTHORISED", "DELETED"],
          description: "Filter by payment status",
        },
      },
    },
  • src/index.ts:261-262 (registration)
    Registration/routing for all payment tools in CallToolRequestSchema handler. Routes 'xero_payments_*' tool calls (including 'xero_payments_list') to handlePaymentTool.
    if (name.startsWith("xero_payments_")) {
      return await handlePaymentTool(name, toolArgs);
  • src/index.ts:79-80 (registration)
    Tool registration: paymentTools array is included in the tool list returned by getAllDomainTools() via getDomainTools('payments').
    case "payments":
      return paymentTools;
  • Helper: XeroClient.get() makes authenticated GET requests to the Xero API, used by the handler to call 'Payments' endpoint.
    async get(path: string, params?: Record<string, string>): Promise<unknown> {
      return this.request("GET", path, params);
Behavior2/5

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

No annotations provided. Description only mentions pagination and status filter, omitting behavior like rate limits, effects of pagination, or that it's a read-only operation.

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

Conciseness5/5

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

Two sentences, no fluff. Purpose is front-loaded. Every word adds value.

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?

Adequate for a simple list tool with good schema. Lacks output schema and details about response structure or how to navigate pages beyond incrementing page number.

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?

Input schema has 100% coverage, with clear descriptions for both parameters. The description ('with pagination', 'optionally filter by status') adds little beyond schema. Baseline 3.

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?

Clear verb 'List', resource 'payments', with specifics: pagination and optional status filter. Distinguishes from sibling tools like xero_payments_get and xero_payments_create.

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?

Implied usage for listing payments, but no explicit when-to-use or when-not-to-use. Mentions optional filter but no alternatives drawn from sibling tools.

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/wyre-technology/xero-mcp'

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