Skip to main content
Glama

Publish or pause booking page

set_booking_page_status
DestructiveIdempotent

Publish or pause your booking page when the user requests it. Publishing makes the URL accept bookings from anyone with the link, after checking timezone and calendar readiness. Pausing prevents new bookings; existing meetings and guest links keep working. Read the page's current version first. Nothing is sent. To delete a page: delete_record(booking_page).

When to use: Publish or pause your page when asked, using its current version. Publishing checks readiness; pausing keeps its URL and existing meetings.

Example: Publish my intro booking page and give me its link.

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": {
      "page_id": "<page_id>",
      "expected_updated_at": "<expected_updated_at>",
      "published": "<published>"
    },
    "name": "set_booking_page_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesYour page ID from get_scheduling_settings.
publishedYestrue accepts new bookings; false pauses the page.
expected_updated_atYesUnchanged 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
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field 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)$"
  3. 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"
      -}
  4. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=true and openWorldHint=true, but the description adds meaningful context: publishing exposes the URL publicly and runs a timezone/calendar readiness check, pausing preserves existing meetings and guest links, and 'Nothing is sent' clarifies there is no outbound communication. It stops short of saying what happens if the readiness check fails or whether the change is reversible, so not a 5.

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?

Front-loaded with the action and its effects, and the delete routing is well placed. The 'When to use' block partly restates the opening sentences ('Publishing checks readiness; pausing keeps its URL and existing meetings'), which is mild redundancy rather than waste.

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 an output schema present, return values need not be explained, and the description covers semantics, prerequisites, side effects and the sibling alternative. The one gap is failure-mode behavior when the readiness check does not pass.

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 baseline would be 3, but the description reinforces the optimistic-concurrency intent behind expected_updated_at ('using its current version', 'Read the page's current version first'), which the schema only states mechanically. It adds genuine meaning about why that parameter exists.

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 pair and resource ('Publish or pause your booking page') and immediately contrasts with the destructive alternative ('To delete a page: delete_record(booking_page)'). An agent can distinguish this from save_booking_page and delete_record 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?

Explicit when-to-use section, a prerequisite ('Read the page's current version first'), and a named alternative tool for the delete case. It also states an example invocation, leaving little to inference.

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