Skip to main content
Glama
panoskiriakopoulos-sys

Rizerve MCP Server

Update Rizerve Property

rizerve_update_property

Update property details by specifying only the fields to change. Modify price, availability, amenities, and more without affecting other settings.

Instructions

Update a property's details. Send only the fields you want to change — omitted fields are left unchanged.

Args:

  • slug (string): Property public slug

  • Any property fields to update (title, description, price_per_night, is_published, etc.)

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

Examples:

  • "Change the villa price to €120" → rizerve_update_property({ slug: "beachfront-villa", price_per_night: 12000 })

  • "Publish the mountain cabin" → rizerve_update_property({ slug: "mountain-cabin", is_published: true })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
slugYesProperty public slug (e.g. "beachfront-villa")
bedroomsNo
latitudeNo
locationNo
amenitiesNo
bathroomsNo
extra_feeNo
longitudeNo
max_guestsNo
descriptionNo
theme_colorNo
is_publishedNo
minimum_stayNo
check_in_timeNo
main_site_urlNo
check_out_timeNo
extra_fee_typeNo
price_per_nightNoPrice per night in property currency (face value, not cents)
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?

The description adds the important PATCH-like behavior that omitted fields remain unchanged, beyond what annotations provide. No contradictions with annotations; the update verb aligns with readOnlyHint=false.

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 concise with a clear structure: behavior statement, args list, and examples. No unnecessary information.

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

Completeness3/5

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

With 20 parameters and no output schema, the description does not mention the return value or error handling, which is a gap. Examples are helpful but incomplete for full context.

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

Parameters3/5

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

Schema coverage is only 15%, and the description lists a few example fields and explains response_format. However, it doesn't add meaning for the majority of parameters (e.g., bedrooms, latitude), relying heavily on schema types and constraints.

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 'Update a property's details' with the key nuance that only sent fields are changed. This distinguishes it from create and delete sibling tools.

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 explicitly says 'Send only the fields you want to change — omitted fields are left unchanged', providing clear when-to-use guidance. Alternatives are implied via sibling tool names but not explicitly mentioned.

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