Skip to main content
Glama
zenskar

Zenskar MCP Server

Official
by zenskar

listJournalLines

listJournalLines

Retrieve paginated journal lines filtered by customer, contract, account, currency, or posted date.

Instructions

Retrieve a paginated list of journal lines (individual debit/credit entries) across all journal entries. Supports filtering by customer, contract, account, currency, and parent journal entry posted date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoCursor for pagination.
limitNoMaximum number of journal lines to return per page.
search_queryNoSearch query to filter journal lines.
orderNoSort order. Prefix with '-' for descending. Defaults to '-created_at'.
customer_idNoFilter by customer UUID.
contract_idNoFilter by billing contract UUID.
account_idNoFilter by GL account UUID.
journal_entry_idNoFilter by parent journal entry UUID.
revenue_contract_idNoFilter by revenue recognition contract UUID (distinct from billing contract_id).
performance_obligation_idNoFilter by performance obligation UUID.
invoice_idNoFilter by invoice UUID.
currencyNoThree-letter ISO currency code (e.g. 'USD').
journal_entry__posted_at__gteNoParent entry posted-at lower bound (inclusive). YYYY-MM-DD or ISO datetime.
journal_entry__posted_at__lteNoParent entry posted-at upper bound (inclusive).
__userContextNoInternal user context for multi-tenant authentication and approval workflow
Behavior2/5

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

With no annotations, the description carries the full burden for behavioral traits. It states the tool returns a paginated list and supports filters, but fails to disclose default behavior, authentication requirements, sort order defaults, or whether it is read-only. Critical gaps remain.

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 two sentences with no wasted words. It front-loads the core purpose and then lists filters. Every sentence 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?

Given the complexity (15 parameters, no output schema, no annotations), the description provides the essential information but omits details on pagination, sort order behavior, and return format. It is adequate but has clear gaps.

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 baseline is 3. The description adds minimal extra meaning by highlighting specific filter capabilities, but does not elaborate on all parameters (e.g., search_query, order, pagination parameters). The schema already describes each parameter adequately.

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 action (Retrieve), resource (journal lines), and scope (across all journal entries). It also mentions supported filters, effectively distinguishing it from sibling tools like listJournalEntries.

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 when needing individual debit/credit entries with specific filters, but does not explicitly state when to use this tool versus alternatives, nor when not to use it. No comparison with other list tools is provided.

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/zenskar/mcp-zenskar'

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