Skip to main content
Glama

List text templates

easybill_list_text_templates
Read-onlyIdempotent

List reusable text templates for document headers, footers, and notes. Filter and paginate to locate standard payment terms and closing wording.

Instructions

List text templates from easybill with optional filters and pagination.

Reusable text blocks for document headers, footers and notes. Handy for reusing your standard payment terms or closing wording when creating a document.

Returns a compact field set by default; pass 'fields' for specific columns or ['all'] for everything.

Returns: { total, count, page, pages, has_more, next_page, items[] }. Use 'next_page' to continue paging. Monetary values are integers in cents (150 = 1.50 EUR).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Use 'next_page' from a previous response to continue.
limitNoItems per page, 1-1000 (default 25). Keep this small unless you need bulk data.
fieldsNoLimit returned columns to these field names (e.g. ['number','amount','paid_at']). Pass ['all'] for every field. Omit for a compact default set. Fewer fields = less context used.
response_formatNoOutput format: 'markdown' for readable prose, 'json' for machine-readable datamarkdown
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable details about pagination via next_page, the default compact field set, and monetary units in cents. The unsupported 'filters' mention is a minor behavioral inaccuracy.

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 concise and well-structured, with an intro, use-case, and return details. Each sentence carries useful information, though the 'filters' phrase is redundant and slightly off-point.

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

Completeness4/5

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

Given no output schema, the description compensates by specifying the return object shape and pagination mechanics. It covers the essential operational context, but the vague 'optional filters' promise is unfulfilled and leaves a minor gap.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning to 'fields' by explaining the compact default set and the option to request all columns, plus reinforcing pagination usage. It does not misinterpret the actual parameters despite the 'filters' mention.

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?

The description clearly states it lists text templates, distinguishing it from siblings like easybill_get_text_template. However, the claim of 'optional filters' is misleading because no filter parameter exists in the schema, slightly detracting from clarity.

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?

It provides useful context by describing text templates as reusable blocks for headers, footers, and notes, with an example use case. It does not explicitly contrast with alternatives or state when not to use it, but the use case is clear.

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/stack74/easybill-mcp'

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