Lodgify MCP Server

update_booking_status

Modify booking statuses in Lodgify by providing a booking ID and new status such as Booked, Cancelled, CheckedIn, or CheckedOut.

Instructions

Update the status of an existing booking.

Args:
    booking_id: The unique ID of the booking
    status: New status (e.g., "Booked", "Cancelled", "CheckedIn", "CheckedOut")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "booking_id": "<booking_id>",
      "status": "<status>"
    },
    "name": "update_booking_status"
  }
}

Input Schema

Name	Required	Description	Default
`booking_id`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jan 31, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't cover permissions needed, whether changes are reversible, error conditions (e.g., invalid status), or response format. This leaves significant gaps for a mutation tool.

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 front-loaded with the core purpose in the first sentence, followed by a concise Args section. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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?

Given the tool's complexity (mutation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain behavioral aspects like side effects, error handling, or return values, which are critical for safe and effective use by an AI agent.

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 description coverage is 0%, so the description must compensate. It adds meaningful context: 'booking_id' is explained as 'The unique ID of the booking', and 'status' includes examples ('Booked', 'Cancelled', etc.). This clarifies parameter purposes beyond the schema's basic types, though it could specify format constraints (e.g., status enum).

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 the verb ('Update') and resource ('status of an existing booking'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'create_booking' or 'get_booking_by_id' beyond the implied update vs. create/read distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., booking must exist), exclusions, or comparisons to siblings like 'create_booking' for new bookings or 'get_booking_by_id' for viewing status.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server