opentable-mcp

Overview Schema Source Related Servers Discussions Admin

opentable_modify_preview

Preview changes to an existing OpenTable reservation and get the new cancellation policy, card re-hold details, and modify token needed before applying the update.

Instructions

Preview a MODIFICATION to an existing OpenTable reservation. Takes the existing reservation's identity (restaurant_id + confirmation_number + security_token from opentable_list_reservations or the original opentable_book result) plus the NEW slot args (from a fresh opentable_find_slots call) and returns the new cancellation_policy, CC re-hold details, and a modify_token that opentable_modify consumes. Mirrors opentable_book_preview, but the /booking/details URL includes confirmationNumber + securityToken + isModify=true so OpenTable's SSR returns the modify state. dining_area_id is OPTIONAL — omitted, it's auto-resolved from the booking-details page like book_preview does. REQUIRED before opentable_modify — no shortcut path. For Listing-type restaurants the modify can't proceed (no slot picker); check opentable_get_restaurant.bookable first.

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": {
      "restaurant_id": "<restaurant_id>",
      "confirmation_number": "<confirmation_number>",
      "security_token": "<security_token>",
      "date": "<date>",
      "time": "<time>",
      "party_size": "<party_size>",
      "reservation_token": "<reservation_token>",
      "slot_hash": "<slot_hash>"
    },
    "name": "opentable_modify_preview"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	YYYY-MM-DD (the NEW date)
`time`	Yes	HH:MM (24h) — the NEW time
`slot_hash`	Yes	slot_hash from opentable_find_slots for the NEW slot
`party_size`	Yes
`experience_id`	No	For Experience-mandatory slots; required when the new slot has experience_ids.
`restaurant_id`	Yes
`dining_area_id`	No	Optional dining-area (room) id for the NEW slot. When omitted, auto-resolved to the default dining area from OpenTable's booking-details page — the same resolution opentable_book_preview uses. Pass explicitly only to pin a specific room.
`experience_ids`	No	Pass-through from find_slots.experience_ids. When non-empty, experience_id must also be set.
`security_token`	Yes
`database_region`	No	OpenTable's sharded-database region for the restaurant. Defaults to 'NA' (North America). Pass the venue's region (e.g. for UK/EU/APAC restaurants) when booking or cancelling outside North America — slot-lock, availability, and cancel route to the wrong database shard, or fail opaquely, when this is wrong. LIMITATION: not auto-derived from restaurant data (OpenTable's availability/booking responses don't surface the shard id), so non-NA bookings must set it explicitly.
`reservation_token`	Yes	slot_availability_token from opentable_find_slots for the NEW slot
`confirmation_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.3.4Oct 17, 2026
- addedInput schema / properties / date / pattern
```
Added value: +"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
```
- addedInput schema / properties / time / pattern
```
Added value: +"^([01]\\d|2[0-3]):[0-5]\\d$"
```

Changed1 schema field changedv1.0.0Sep 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedv0.18.2Sep 3, 2026

addedInput schema / properties / dining_area_id / description

Added value: +"Optional dining-area (room) id for the NEW slot. When omitted, auto-resolved to the default dining area from OpenTable's booking-details page — the same resolution opentable_book_preview uses. Pass explicitly only to pin a specific room."

changedInput schema / required

Previous value: -[
-  "restaurant_id",
-  "confirmation_number",
-  "security_token",
-  "date",
-  "time",
-  "party_size",
-  "reservation_token",
-  "slot_hash",
-  "dining_area_id"
-]New value: +[
+  "restaurant_id",
+  "confirmation_number",
+  "security_token",
+  "date",
+  "time",
+  "party_size",
+  "reservation_token",
+  "slot_hash"
+]

First observedv0.14.3Jul 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) cover the safety profile, and the description goes well beyond them: it discloses the return payload (new cancellation_policy, CC re-hold details, modify_token), the internal /booking/details URL construction with isModify=true, and the Listing-type failure mode. It is a preview that yields a token rather than performing the change, which is clearly conveyed.

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?

Purpose and the identity-vs-new-slot split are front-loaded, then constraints (dining_area_id optional, required-before-modify, Listing-type block) follow. It is dense and slightly repetitive on provenance, but nearly every sentence carries operational information and nothing is filler.

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?

For a 12-parameter, no-output-schema tool, the description supplies what is otherwise missing: the returned artifacts (cancellation_policy, CC re-hold, modify_token), the workflow position (must precede opentable_modify), and the non-NA database_region caveat is documented in the schema. Nothing an agent needs to call this correctly is absent.

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 67%, and the description adds real meaning beyond it: it groups the params conceptually (existing identity vs NEW slot args) and explains origin/staleness ('from a fresh opentable_find_slots call'). It also reinforces dining_area_id as optional with auto-resolution. Some of this (slot_hash/reservation_token provenance) is already in the schema, so it is additive rather than filling a large gap.

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?

States a specific verb+resource ('Preview a MODIFICATION to an existing OpenTable reservation') and explicitly distinguishes itself from siblings opentable_book_preview ('Mirrors opentable_book_preview, but...') and opentable_modify ('modify_token that opentable_modify consumes'). An agent can tell why this preview exists versus a plain booking preview without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('REQUIRED before opentable_modify — no shortcut path') and where each input originates (identity from opentable_list_reservations or opentable_book, new slot args from a fresh opentable_find_slots call). Also names a when-not case: Listing-type restaurants can't proceed and you should check opentable_get_restaurant.bookable first.

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

Deploy Server