Skip to main content
Glama
Xero MCP Server

Xero MCP Server

Official
by XeroAPI

create-manual-journal

Create a balanced manual journal in Xero with narration and at least two debit/credit journal lines using account codes. Define draft or posted entries for accurate accounting records.

Instructions

Create a manual journal in Xero. Retrieve a list of account codes in Xero to use for the journal lines. Journal lines must contain at least two individual journal lines with account codes, use basic accounting account types pairing when not specified, and make sure journal line pairs have credit and debit balanced.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "narration": "<narration>",
      "manualJournalLines": "<manualJournalLines>"
    },
    "name": "create-manual-journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOptional URL link to a source document
dateNoOptional date in YYYY-MM-DD format
statusNoOptional status of the manual journal (DRAFT, POSTED, DELETED, VOIDED, ARCHIVED), DRAFT by default
narrationYesDescription of manual journal being posted
lineAmountTypesNoOptional line amount types (EXCLUSIVE, INCLUSIVE, NO_TAX), NO_TAX by default
manualJournalLinesYesThe manualJournalLines element must contain at least two individual manualJournalLine sub-elements
showOnCashBasisReportsNoOptional boolean to show on cash basis reports, default is true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.0.18
    • changedInput schema / properties / status / description
      Previous value: -"Optional status of the manual journal (DRAFT, POSTED, DELETED, VOID, ARCHIVED), DRAFT by default"New value: +"Optional status of the manual journal (DRAFT, POSTED, DELETED, VOIDED, ARCHIVED), DRAFT by default"
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "DRAFT",
      -  "POSTED",
      -  "DELETED",
      -  "VOID",
      -  "ARCHIVED"
      -]New value: +[
      +  "DRAFT",
      +  "POSTED",
      +  "DELETED",
      +  "VOIDED",
      +  "ARCHIVED"
      +]
  2. Addedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses a genuine domain constraint not present in the schema — that debit/credit pairs must balance and that basic accounting account-type pairing should be applied when unspecified — but says nothing about permissions, side effects, idempotency, or whether the journal posts immediately versus staying in DRAFT.

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 content is relevant but delivered as a comma-spliced run-on sentence with uneven spacing. The 'at least two lines' rule restates the schema's own constraint, while the more valuable balancing rule is buried mid-sentence rather than front-loaded.

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?

For a 7-parameter mutation with no annotations and no output schema, the description covers the essential validation rules but omits what the call returns (e.g., journal ID) and the effect of the status field. It is adequate to attempt a correct call but incomplete on outcomes.

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 the schema already documents every field including enums and the debit-positive/credit-negative convention. The description adds only the balancing/pairing convention for lines, not meaning for any individual parameter; baseline 3 applies.

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?

Opens with a specific verb+resource ('Create a manual journal in Xero'), which is unambiguous. It does not, however, distinguish this from the sibling 'update-manual-journal' or clarify that it always creates a new record rather than modifying one.

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?

It usefully tells the agent to first retrieve account codes (implying a list-accounts lookup) before building lines, which is real workflow guidance. It gives no explicit when-not or routing to 'update-manual-journal' versus this tool, so the alternative selection is left to inference.

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