Retrieves a booking page by UUID with all of its configured settings, enabling AI agents to inspect page details before updates or scheduling actions.
One booking page with every setting (GET /api/v1/booking-pages/{id}). Requires calendar:view.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | booking page UUID |
Changes observed during successful MCP inspections.
v4.71.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full disclosure burden. It usefully states the required calendar:view permission and the GET endpoint implies a read-only retrieval, but it does not describe error behavior, rate limits, or detailed return characteristics beyond "every setting."
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two compact sentences, front-loads the retrieval scope, and includes the permission requirement without wasted wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-resource GET with one fully documented parameter, the description covers scope and access requirement adequately. It could be richer about return shape or errors, but the complexity is low enough that this is not a major gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage for the single id parameter, so the baseline is 3. The description's {id} endpoint reference does not add syntax or meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: retrieving one booking page with every setting via GET /api/v1/booking-pages/{id}. The phrase "One booking page" also distinguishes it from the sibling list_booking_pages operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It adds a clear prerequisite by stating "Requires calendar:view," which helps an agent know access requirements. However, it does not explicitly say when to use this versus list_booking_pages or other booking-page tools, so usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.