Buchhaltungsbutler MCP

Postings: get postings

postings_list

Read-onlyIdempotent

Retrieve booking journal postings for a specified customer account, filtered by date range or account. Get up to 1000 postings per request with limit and offset for pagination.

Instructions

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records.

get postings

Get postings for a specified customer account. The response includes the number of returned rows and an array of postings data. NOTE: Each request is limited to 1000 postings!

Use to read the booking journal, filtered by date range or posting account.

Supports limit and offset. Ask for a bounded date range rather than paging through a whole financial year.

Endpoint: POST /postings/get

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Set a limit of returned postings. NOTE: the maximum limit is 1000!
`order`	No	Possible values are "default", "date ASC", "date DESC", "date_last_action ASC", "date_last_action DESC", "id_by_customer ASC", "id_by_customer DESC". The default order is ascending by date as first and date_last_action as second criterion. Please not that the validation of the specified value is case sensitive!
`offset`	No	Set an offset for the returned postings.
`account`	No	A comma separated list of accounts. Use the following options: all, all financial accounts, free booking and any of your available accounts as numeric value. The default is "all"
`date_to`	Yes	The postings issuing date in format 'YYYY-MM-DD' (e.g. '2017-04-26'). All postings with issuing date including and before given value will be returned. If specified, the field will be validated. An empty string is not considered a valid date.
`date_from`	Yes	The postings issuing date in format 'YYYY-MM-DD' (e.g. '2017-04-26'). All postings with issuing date including and after given value will be returned. If specified, the field will be validated. An empty string is not considered a valid date.
`cost_location`	No	Set a specific cost location code. If specified, only postings to this cost location are returned
`posting_status`	No	Set the status of the posting. You have the following options: all, fixed, unfixed The default is "all"
`postingaccount`	No	A comma separated list of postingaccounts. Use the following options: all, all postingaccounts, all debtors, all creditors and any of your available postingaccounts as numeric value. The default is "all"
`date_last_action_to`	No	A date in format 'YYYY-MM-DD'. All postings that were created or modified in status (confirmed, fixed) on or before this date will be returned. If specified, the field will be validated. An empty string is not considered a valid date.
`date_last_action_from`	No	A date in format 'YYYY-MM-DD'. All postings that were created or modified in status (confirmed, fixed) on or after this date will be returned. If specified, the field will be validated. An empty string is not considered a valid date.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	An array of postings data
`rows`	No	Number of returned rows
`message`	No	blank
`success`	Yes	Success boolean

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.1.3Sep 26, 2026
- changedOutput schema / properties / data / items / properties / booking_number / type
```
Previous value: -"string"New value: +[
+  "string",
+  "integer"
+]
```
- changedOutput schema / properties / data / items / properties / date_delivery / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / receipt_id_by_customer / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / transaction_amount / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / transaction_id_by_customer / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Addedv1.1.2Sep 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds important operational behavior beyond that: the 1000-postings request limit, the response shape (number of returned rows plus an array of postings), support for limit/offset, and guidance to prefer bounded date ranges over pagination. No contradiction with annotations.

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?

Well-structured with read-only status, function, limit, use case, and pagination advice leading into the endpoint. Minor redundancy exists in repeating 'get postings' under the title and restating read-only facts that annotations already provide, but each sentence otherwise contributes usable guidance.

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

Completeness5/5

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

Complete for a complex 11-parameter tool: annotations cover safety/idempotence, schema covers all parameter details, output schema covers return values, and the description supplies rate-limit, response-structure, and pagination strategy context. No critical calling information is missing.

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?

Although the input schema covers all 11 parameters at 100%, the description adds semantic value by tying filters to use cases ('filtered by date range or posting account') and explaining the intended interaction between limit/offset and date-range bounds. This goes beyond the schema's per-parameter descriptions without replacing them.

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?

States a specific operation ('Get postings' / 'read the booking journal') and resource, and clearly frames itself as a read operation ('🟢 READ-ONLY: Fetches data. Makes no changes'), separating it from sibling postings tools like postings_create_free and postings_cancel. The mention of filtered postings resolves what is being listed.

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

Usage Guidelines4/5

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

Explicitly says 'Use to read the booking journal, filtered by date range or posting account' and gives selection advice about requesting a bounded date range instead of paging through a whole financial year. It does not enumerate exclusions or name alternative tools, but the read-only framing plus the postings-specific verb makes the intended use clear.

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

Deploy Server