Skip to main content
Glama

conduyt_update_booking_page

Updates a booking page with only the provided fields changed, including availability, Zoom video, form fields, payments, and branding.

Instructions

Update a booking page (PATCH /api/v1/booking-pages/{id}): only the fields given change. videoProvider 'zoom' turns on one Zoom meeting per booking (null turns it off and clears the host); videoHostEmail must be a user of the connected Zoom account (null = the app's own user). Requires calendar:edit (admin/owner).

Input Schema

NameRequiredDescriptionDefault
idYesbooking page UUID
slugNopublic slug (conduyt.app/book/<slug>)
colorNohex colour
titleNopage title
userIdNohost user UUID (the page owner)
logoUrlNo
reviewsNo
campaignNo
gdprTextNo
hyrosTagNo
isActiveNo
locationNowritten location (link, phone, address); with videoProvider zoom it is the fallback when Zoom is down
templateNonull = the default page, 'bda' = the BDA template
brandNameNowhite-label name shown on the page and in Zoom meeting names
eventTypeNo
remindersNo
formFieldsNo
leadSourceNolead source stamped on contacts the page creates
bufferAfterNominutes blocked after each booking
descriptionNo
gdprEnabledNo
gdprLinkUrlNo
hostGroupIdNo
hostUserIdsNousers on this account who can host
redirectUrlNowhere the visitor goes after booking
bufferBeforeNominutes blocked before each booking
embedEnabledNo
hideBrandingNo
maxAttendeesNo
requirePhoneNo
fieldMappingsNo
minimumNoticeNoearliest booking, minutes from now
paymentAmountNocents
stripePriceIdNo
videoProviderNo'zoom' = a new Zoom meeting for every booking (needs conduyt_zoom_connect); null = the written location only
enableIcalFeedNotrue issues a new iCal feed token, false revokes it
hostPrioritiesNohost user id to priority
maxAdvanceDaysNohow far ahead visitors may book
paymentEnabledNoaccepted, but checkout is not implemented yet: the page stays unpaid and the answer carries a warning
videoHostEmailNothe Zoom user the meeting is created under (a user of the connected Zoom account); null = the app's own user
customQuestionsNo
durationMinutesNo
durationOptionsNoselectable durations; empty or null clears
paymentCurrencyNo
stripeProductIdNo
thankYouMessageNo
waitlistEnabledNo
documentsEnabledNothe documents step: the public upload-url and documents routes answer for this page's bookings (bank statements and funding agreements attached to the lead)
documentsPageUrlNothe site page the confirmation email links the visitor back to for the upload (https; the page reads ?appointment=<id>); null = no link
availabilityRulesNoavailability override; null = the host's own rules
maxBookingsPerDayNo
distributionMethodNo
embedAllowedOriginsNoorigins allowed to embed/call the page; null or empty = any

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does meaningful work: it declares the permission model (calendar:edit, admin/owner), the partial-mutation guarantee, and a concrete side effect ('null turns it off and clears the host') that an agent could not infer from the schema. It stops short of describing the return payload or error/validation behavior for a 53-field mutation.

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?

Three dense sentences with the partial-update rule front-loaded, then the two highest-risk parameters with their null semantics, then the auth requirement. No filler and no repetition of structured data.

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?

For a 53-parameter mutation with no annotations and no output schema, the description is far too thin: it omits how the response represents the updated page, whether validation errors are returned per field, and the meaning of null/omission for the vast majority of parameters. It is adequate only for the two video fields it covers.

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

Parameters2/5

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

Schema description coverage is only 49% across 53 parameters, so the description must compensate, yet it explains only videoProvider and videoHostEmail in detail. Many ambiguous fields (reviews, campaign, hyrosTag, stripePriceId, customQuestions, distributionMethod) have no description in either the schema or the prose, leaving half the surface undocumented.

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 names a specific verb and resource ('Update a booking page') and includes the exact route (PATCH /api/v1/booking-pages/{id}), which unambiguously distinguishes it from the create/get/list booking-page siblings in the same namespace.

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?

It states the operative usage rule ('only the fields given change', i.e. partial update) and the authorization prerequisite ('Requires calendar:edit (admin/owner)'), plus the zoom prerequisite via 'needs conduyt_zoom_connect' in the schema. It does not explicitly say when to choose this over conduyt_create_booking_page or when not to use it, so it falls short of 5.

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

Deploy Server

Other Tools