Booking management

update_booking_details

Update the guest name and/or special requests on an active verified booking. Empty notes clears requests. Does not alter dates, prices, verified contact details, or other bookings belonging to this customer. Use reschedule_booking for dates or offerings.

View as Markdown

Scope & access

Directory + businessWrites data

Follow the credential fields below. Public discovery does not require a login; private booking operations require the indicated token.

This tool advertises idempotent behavior. If an idempotencyKey is specified, reuse it with identical arguments only when retrying that same intended action.

Parameters

These are the directory endpoint parameters. Business endpoints scope public discovery to the published business; owner calls still require businessId. Inspect tools/list on your endpoint for the exact schema.

bookingIdRequired

string

Parent booking ID from create_hold (holdId), confirm_booking, or list_bookings. Never pass a child allocation ID.

accessTokenRequired

string

Secret accessToken returned after verification/confirmation or access recovery. Never invent or expose it publicly.

nameOptional

string

New guest name for this booking only; does not rename the customer's other bookings.

notesOptional

string

Replace special requests/notes; empty string clears them. Requests are subject to business acceptance.

idempotencyKeyRequired

string

Generate a UUID per intended mutation. Reuse the same key and identical parameters only when retrying that action.

Example call

Pass this object to the MCP client's callTool method. Replace placeholders with returned IDs, saved credentials and the customer's details; use future dates appropriate to their request.

update_booking_details · MCP client arguments

json

{
  "name": "update_booking_details",
  "arguments": {
    "bookingId": "<bookingId>",
    "accessToken": "<saved-access-token>",
    "idempotencyKey": "<new-UUID-for-this-action>",
    "notes": "Late arrival requested."
  }
}

JSON schemas

Nested fields, formats, enums and constraints are included in the complete schemas. Successful data is returned in structuredContent. SDK input validation and domain errors use different error shapes.

Input schemaJSON Schema

Input JSON Schema

json

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "bookingId": {
      "type": "string",
      "minLength": 1,
      "description": "Parent booking ID from create_hold (holdId), confirm_booking, or list_bookings. Never pass a child allocation ID."
    },
    "accessToken": {
      "type": "string",
      "minLength": 10,
      "description": "Secret accessToken returned after verification/confirmation or access recovery. Never invent or expose it publicly."
    },
    "name": {
      "description": "New guest name for this booking only; does not rename the customer's other bookings.",
      "type": "string",
      "minLength": 1,
      "maxLength": 120
    },
    "notes": {
      "description": "Replace special requests/notes; empty string clears them. Requests are subject to business acceptance.",
      "type": "string",
      "maxLength": 1000
    },
    "idempotencyKey": {
      "type": "string",
      "minLength": 8,
      "maxLength": 200,
      "description": "Generate a UUID per intended mutation. Reuse the same key and identical parameters only when retrying that action."
    }
  },
  "required": [
    "bookingId",
    "accessToken",
    "idempotencyKey"
  ]
}

Output schemaJSON Schema

Output JSON Schema

json

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "bookingId": {
      "type": "string"
    },
    "name": {
      "type": [
        "string",
        "null"
      ]
    },
    "notes": {
      "type": [
        "string",
        "null"
      ]
    },
    "status": {
      "type": "string",
      "enum": [
        "held",
        "pending_verification",
        "pending_payment",
        "pending_approval",
        "confirmed",
        "cancelled",
        "expired",
        "no_show",
        "completed"
      ]
    }
  },
  "required": [
    "bookingId",
    "name",
    "notes",
    "status"
  ],
  "additionalProperties": false
}

Behavior annotationsMCP

Tool annotations

json

{
  "readOnlyHint": false,
  "destructiveHint": false,
  "idempotentHint": true,
  "openWorldHint": true
}

Errors & next steps

Check isError before reading a success response. Follow nextStep where supplied, and never treat a pending booking as confirmed. See Errors and retries and the booking lifecycle for recovery paths.

Back to all tools