Skip to main content
Glama
panoskiriakopoulos-sys

Rizerve MCP Server

List Rizerve Bookings

rizerve_list_bookings
Read-onlyIdempotent

Retrieve and filter bookings across properties by status, property, or date range. Get paginated results with guest details and pricing.

Instructions

List bookings across all properties with optional filters.

Supports filtering by status, property, and date range. Results are paginated.

Args:

  • page (number): Page number (default: 1)

  • limit (number): Items per page, max 100 (default: 20)

  • status (string): Filter by status: pending, confirmed, cancelled, completed

  • property_slug (string): Filter by property slug

  • check_in_from (date): Show bookings from this date (YYYY-MM-DD)

  • check_in_to (date): Show bookings up to this date (YYYY-MM-DD)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Paginated booking list with full guest details, pricing, and status.

Examples:

  • "Show all confirmed bookings" → rizerve_list_bookings({ status: "confirmed" })

  • "What bookings check in this week?" → rizerve_list_bookings({ check_in_from: "2026-06-27", check_in_to: "2026-07-04" })

  • "Show pending bookings for the villa" → rizerve_list_bookings({ property_slug: "beachfront-villa", status: "pending" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based)
limitNoItems per page (max 100)
statusNoFilter by booking status
check_in_toNoFilter bookings checking in on or before this date (YYYY-MM-DD)
check_in_fromNoFilter bookings checking in on or after this date (YYYY-MM-DD)
property_slugNoFilter by property slug
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already declare readOnlyHint, so the description's disclosure of pagination, output format switching, and return details (guest info, pricing, status) adds significant behavioral context beyond the annotations, which are minimal. No contradictions.

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 well-structured with a brief summary, a clear parameter list using the Args format, and concise examples. Every sentence adds value, and the most critical information is front-loaded.

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?

Given the tool has 7 parameters, no required fields, and no output schema, the description covers all essential aspects: pagination, filtering options, output format, and return content. Examples further enhance completeness.

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%, but the description enriches parameters with examples, default values, and usage hints (e.g., date format, status values) that are not in the schema. This helps an agent select and invoke parameters correctly.

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 'List bookings across all properties' with a specific verb and resource, and distinguishes itself from sibling tools like rizerve_get_booking (single booking) through its scope and filtering capabilities.

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 provides clear usage context with filtering options and multiple examples demonstrating different use cases. It implicitly guides when to use this tool (listing with filters) rather than alternatives, though it does not explicitly mention when not to use it.

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/panoskiriakopoulos-sys/rizerve-mcp-server'

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