Skip to main content
Glama
panoskiriakopoulos-sys

Rizerve MCP Server

List Rizerve Properties

rizerve_list_properties
Read-onlyIdempotent

Retrieve a paginated list of your properties with full details including pricing, amenities, and availability. Filter by published status and choose markdown or JSON output.

Instructions

List all properties owned by the authenticated account.

This tool returns properties with full details including pricing (in cents), amenities, availability settings, and branding configuration.

Args:

  • page (number): Page number, 1-based (default: 1)

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

  • published_only (boolean): Filter to published only (default: false)

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

Returns: For JSON format: Paginated response with { data: Property[], meta: { total, page, limit } } For markdown format: Formatted list with property details

Examples:

  • "Show all my properties" → rizerve_list_properties()

  • "Show published properties" → rizerve_list_properties({ published_only: true })

  • "Get properties as JSON" → rizerve_list_properties({ response_format: 'json' })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based)
limitNoItems per page (max 100)
published_onlyNoFilter to published properties only
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, idempotentHint, and destructiveHint. The description adds value by detailing the return content (pricing in cents, amenities, availability settings, branding configuration) and output format options.

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?

Well-structured with Args, Returns, and Examples sections. No unnecessary text; every sentence adds value. Front-loaded with purpose.

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?

Despite no output schema, the description fully explains return format for both JSON and markdown, including the pagination structure. All parameters are documented with examples.

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 adds clarity with examples and explains the response_format enum values ('markdown' vs 'json'). It provides concrete usage patterns.

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 'List all properties owned by the authenticated account.' This is a specific verb (list) and resource (properties), and it distinguishes from sibling tools that deal with bookings, availability, etc.

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?

No explicit statement about when to use this tool versus alternatives. However, sibling tool names like rizerve_get_property (single property) and rizerve_list_bookings imply when this tool is appropriate.

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