Skip to main content
Glama

list_holidays

Query leave bookings for your organisation using filters like date range, status, user or department. Results are paginated for easy browsing.

Instructions

Query leave bookings ("holidays") for the organisation.

All filters are optional. Results are paginated at 100 per page — use page_number and read totalRecords/nextPageLink in the response.

Args: start: Include holidays on or after this date-time (ISO 8601). end: Include holidays before and including this date-time (ISO 8601). status: Filter by status. Defaults to pending + approved if omitted. user_ids: Comma-separated user IDs to include (e.g. "12,34"). exclusion_user_ids: Comma-separated user IDs to exclude. department_id: Only holidays for this department. leave_type_id: Only holidays of this leave type. approver_id: Only holidays approved by this user. my_team_only: Restrict to the team of this user ID. my_favourites_only: Restrict to the favourite users of this user ID. department_managers_only: Only holidays for department managers. non_archived_users_only: Exclude archived users. transaction_year: Filter to this transaction year. page_number: Page to fetch (defaults to 1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
startNo
statusNo
user_idsNo
approver_idNo
page_numberNo
my_team_onlyNo
department_idNo
leave_type_idNo
transaction_yearNo
exclusion_user_idsNo
my_favourites_onlyNo
non_archived_users_onlyNo
department_managers_onlyNo
Behavior3/5

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

With no annotations, the description carries full burden. It discloses pagination (100 per page, totalRecords/nextPageLink) and optional filters. However, it does not mention authorization, rate limits, or performance implications.

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?

The description is well-structured with a clear intro and per-parameter explanations. It is front-loaded with purpose and pagination. Slightly verbose, but every part adds value.

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 14 optional parameters and no output schema, the description covers pagination and all filters. It mentions response fields (totalRecords/nextPageLink), but lacks details on the structure of individual holiday records.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description provides detailed semantics for all 14 parameters (e.g., 'start: Include holidays on or after this date-time (ISO 8601)'). This adds significant value beyond schema field titles.

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 'Query leave bookings ("holidays") for the organisation.' The verb 'query' is precise for a list operation, and it distinguishes from siblings like book_holiday (create) and get_holiday (single).

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?

The description says 'All filters are optional.' and explains pagination. It implies usage for listing holidays, but does not explicitly contrast with siblings like list_absences or provide when-not-to-use scenarios.

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/mlequime/timetastic-mcp'

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