Skip to main content
Glama
panoskiriakopoulos-sys

Rizerve MCP Server

Create Rizerve Property

rizerve_create_property

Add new rental properties to the Rizerve platform by providing a title and nightly rate, with optional details like location, amenities, and capacity.

Instructions

Create a new property listing.

Required fields: title, price_per_night (in cents). Optional: description, location, public_slug (auto-generated if omitted), bedrooms, bathrooms, max_guests, amenities, minimum_stay, check_in_time, check_out_time, extra_fee, extra_fee_type, theme_color, latitude, longitude, main_site_url.

Args:

  • title (string): Property title (required)

  • price_per_night (number): Price in cents, e.g. 15000 = €150.00 (required)

  • All other fields optional (see schema)

Returns: Created property object with generated id and public_slug.

Examples:

  • "Add a new villa in Crete" → rizerve_create_property({ title: "Cretan Sunset Villa", price_per_night: 12000, location: "Crete, Greece", bedrooms: 3, max_guests: 6 })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesProperty name
bedroomsNoNumber of bedrooms
currencyNoISO 4217 currency codeEUR
latitudeNoLatitude coordinate
locationNoLocation (e.g. "Crete, Greece")
amenitiesNoList of amenity tags
bathroomsNoNumber of bathrooms
extra_feeNoExtra fee in euros
longitudeNoLongitude coordinate
max_guestsNoMaximum guest capacity
descriptionNoFull property description
theme_colorNoBrand color (hex)
minimum_stayNoMinimum nights per booking
check_in_timeNoCheck-in time (HH:MM)
main_site_urlNoExternal website URL
check_out_timeNoCheck-out time (HH:MM)
extra_fee_typeNoFee type: fixed or percentage
price_per_nightYesPrice per night in euros (e.g. 150 = €150.00)
response_formatNoOutput format: 'markdown' or 'json'markdown
Behavior3/5

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

Annotations (readOnlyHint=false, destructiveHint=false) indicate a non-destructive write. The description adds that it creates and returns a property object, but does not disclose side effects (openWorldHint=true). No annotation contradiction, but no extra behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description includes an example and lists parameters, but it is somewhat lengthy and contains inaccuracies (title/name, cents/euros). It could be more concise and accurate.

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

Completeness2/5

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

With 19 parameters and no output schema, the description should provide more context (e.g., error handling, authorization). It omits important behavioral details and contains contradictions that reduce completeness.

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

Parameters1/5

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

The description states 'price_per_night (in cents, e.g., 15000 = €150.00)' but the schema says 'Price per night in euros (e.g. 150 = €150.00)'. This is a direct contradiction on units. Additionally, the required parameter is named 'title' in description vs 'name' in schema, adding confusion.

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 'Create a new property listing' and provides an example. However, it incorrectly refers to the required field as 'title' while the schema specifies 'name', which could confuse an AI agent about the correct parameter.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use vs. alternatives like rizerve_update_property. The example is helpful but underspecified, and the contradiction in required fields undermines reliable usage.

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