Skip to main content
Glama

Save booking page

save_booking_page
DestructiveIdempotent

Create a private booking-page draft or edit one of your pages. Creation requires topic and a new request_id UUID; reuse the exact UUID and details on retry. Defaults: 30 minutes, 14 days, empty description. To edit, pass page_id and its expected_updated_at; only supplied fields change. Edits preserve the URL and publication state. This never publishes a draft or sends messages. Use set_booking_page_status when the user asks to publish.

When to use: Create a private draft or patch one of your pages. Reuse the creation request_id on retries; editing needs the page's current version. Publishing is a separate requested action.

Example: Create a draft 30-minute intro page with a two-week booking window.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_booking_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoPublic meeting name; required when creating a draft.
page_idNoExisting page ID from get_scheduling_settings; omit for a new draft.
video_urlNoYouTube, Loom or Vimeo link guests watch after booking; an empty string removes it.
request_idNoRequired for creation. A fresh UUID for this draft; reuse on retries.
descriptionNoPublic description; an empty string clears it.
window_daysNoHow many days ahead guests may book.
duration_minNoMeeting length in minutes.
expected_updated_atNoUnchanged updated_at from get_scheduling_settings or the last successful write.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageNo
updatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / video_url
      Added value: +{
      +  "description": "YouTube, Loom or Vimeo link guests watch after booking; an empty string removes it.",
      +  "maxLength": 500,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changed
    • removedInput schema / properties / page_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / request_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. Changed4 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / page / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / page / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real context: 'This never publishes a draft or sends messages' bounds the blast radius, and 'Edits preserve the URL and publication state / only supplied fields change' defines patch-vs-replace semantics. It does not discuss permission requirements or error/conflict behavior, so it falls short of exhaustive.

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 opening paragraph is dense and front-loaded with the highest-value constraints, but the 'When to use' paragraph largely restates the opening and the closing example adds almost nothing an agent couldn't infer from the defaults already given. Three near-duplicate statements of the create/edit distinction.

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

Completeness4/5

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

With 8 optional parameters, an output schema present, and full annotation coverage, the description covers mode selection, defaults, idempotency, and safety boundaries well enough to invoke correctly. Missing only concurrency-conflict behavior on expected_updated_at mismatches, which matters for a tool using optimistic locking.

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 100%, so the baseline is 3, but the description adds meaning the schema lacks: defaults for duration (30), window (14 days), and description (empty), plus the create-vs-edit parameter pairing (topic + request_id for creation, page_id + expected_updated_at for edits). It stops short of explaining what the UUID reuse actually keys on server-side.

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 first sentence names a specific verb and resource ('Create a private booking-page draft or edit one of your pages') and splits the two operating modes explicitly. It also names the sibling it does not cover ('Use set_booking_page_status when the user asks to publish'), so an agent can disambiguate without opening either 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?

A dedicated 'When to use' section states both modes and the retry condition ('Reuse the creation request_id on retries; editing needs the page's current version'). The only adjacent mutation, publishing, is explicitly routed to set_booking_page_status.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources