Skip to main content
Glama

xero_invoices_create

Create invoices in Xero by specifying type, contact, and line items. Supports sales invoices (ACCREC) and bills (ACCPAY).

Instructions

Create a new invoice in Xero. Requires type, contact, and at least one line item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
TypeYesInvoice type: ACCREC (sales invoice) or ACCPAY (bill) (required)
ContactIDYesThe contact ID to create the invoice for (required)
LineItemsYesArray of line items (required). Each item needs Description, Quantity, UnitAmount, and AccountCode.
DateNoInvoice date in YYYY-MM-DD format
DueDateNoDue date in YYYY-MM-DD format
ReferenceNoInvoice reference/PO number
StatusNoInitial invoice status (default: DRAFT)

Implementation Reference

  • Schema definition for the xero_invoices_create tool. Defines the input schema with required fields Type, ContactID, LineItems and optional fields Date, DueDate, Reference, Status.
    {
      name: "xero_invoices_create",
      description:
        "Create a new invoice in Xero. Requires type, contact, and at least one line item.",
      inputSchema: {
        type: "object",
        properties: {
          Type: {
            type: "string",
            enum: ["ACCREC", "ACCPAY"],
            description:
              "Invoice type: ACCREC (sales invoice) or ACCPAY (bill) (required)",
          },
          ContactID: {
            type: "string",
            description: "The contact ID to create the invoice for (required)",
          },
          LineItems: {
            type: "array",
            description: "Array of line items (required). Each item needs Description, Quantity, UnitAmount, and AccountCode.",
            items: {
              type: "object",
              properties: {
                Description: {
                  type: "string",
                  description: "Line item description",
                },
                Quantity: {
                  type: "number",
                  description: "Quantity",
                },
                UnitAmount: {
                  type: "number",
                  description: "Unit price",
                },
                AccountCode: {
                  type: "string",
                  description: "Account code for the line item",
                },
                TaxType: {
                  type: "string",
                  description: "Tax type code (e.g., OUTPUT, INPUT, NONE)",
                },
              },
              required: ["Description", "Quantity", "UnitAmount", "AccountCode"],
            },
          },
          Date: {
            type: "string",
            description: "Invoice date in YYYY-MM-DD format",
          },
          DueDate: {
            type: "string",
            description: "Due date in YYYY-MM-DD format",
          },
          Reference: {
            type: "string",
            description: "Invoice reference/PO number",
          },
          Status: {
            type: "string",
            enum: ["DRAFT", "SUBMITTED", "AUTHORISED"],
            description: "Initial invoice status (default: DRAFT)",
          },
        },
        required: ["Type", "ContactID", "LineItems"],
      },
  • Handler logic for xero_invoices_create. Extracts args, builds the invoice payload object, optionally adds optional fields, then POSTs to the Xero 'Invoices' endpoint and returns the response as JSON.
    case "xero_invoices_create": {
      const { Type, ContactID, LineItems, Date, DueDate, Reference, Status } =
        args as {
          Type: string;
          ContactID: string;
          LineItems: unknown[];
          Date?: string;
          DueDate?: string;
          Reference?: string;
          Status?: string;
        };
    
      const invoice: Record<string, unknown> = {
        Type,
        Contact: { ContactID },
        LineItems,
      };
      if (Date) invoice.Date = Date;
      if (DueDate) invoice.DueDate = DueDate;
      if (Reference) invoice.Reference = Reference;
      if (Status) invoice.Status = Status;
    
      const response = await client.post("Invoices", {
        Invoices: [invoice],
      });
      return {
        content: [{ type: "text", text: JSON.stringify(response, null, 2) }],
      };
    }
  • src/index.ts:31-31 (registration)
    Import of invoiceTools (which includes xero_invoices_create schema) and handleInvoiceTool from the invoices domain module into the main server.
    import { invoiceTools, handleInvoiceTool } from "./domains/invoices.js";
  • src/index.ts:258-259 (registration)
    Routing of tool calls starting with 'xero_invoices_' (including xero_invoices_create) to the handleInvoiceTool handler.
    if (name.startsWith("xero_invoices_")) {
      return await handleInvoiceTool(name, toolArgs);
  • The XeroClient.post() method used by the handler to send the POST request to the Xero API.
    async post(path: string, body: unknown): Promise<unknown> {
      return this.request("POST", path, undefined, body);
    }
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states 'create a new invoice', which is a generic write operation. It does not disclose potential side effects, error conditions, permissions required, or return values. The description adds little beyond the tool name.

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?

The description is a single sentence that immediately identifies the purpose. It is efficient and front-loaded with the action and resource, with no unnecessary words.

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

Completeness2/5

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

The output schema is absent, so the description should clarify return value. It does not. The tool has 7 parameters, but the description only covers the required ones. For a creation tool, missing details about optional parameters and expected outputs leave an incomplete picture.

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?

With 100% schema description coverage, the baseline is 3. The description adds no new semantic information beyond what the schema already provides; it simply reiterates that certain fields are required. No additional context about parameter relationships or constraints is given.

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 resource 'invoice in Xero', and highlights required fields (type, contact, line items). This distinguishes it from sibling tools like xero_invoices_get or xero_invoices_list, which are read-only.

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 implies usage by listing required components (type, contact, line items), but does not explicitly state when to use this tool over alternatives like xero_contacts_create or xero_invoices_update_status. Some guidance is present, but it is minimal.

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