Skip to main content
Glama

Delete a booking page

well_delete_booking_page
Destructive

Delete one booking page. Call this when the user asks to delete a booking page they named. Its link stops working. If it was the main page, the oldest other page becomes the main page, and the reply names it with its link.

Input Schema

NameRequiredDescriptionDefault
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
booking_page_idYesThe id of the booking page to delete, from a list or get result.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
errorNo
deletedNo
messageYes
successYes
new_defaultNo
reconnect_linkNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / deleted / properties / calendar_view
      Added value: +{
      +  "enum": [
      +    "month",
      +    "two_weeks"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / deleted / properties / theme
      Added value: +{
      +  "enum": [
      +    "dark",
      +    "light"
      +  ],
      +  "type": "string"
      +}
    • removedOutput schema / properties / deleted / properties / weekdays
      Removed value: -{
      -  "items": {
      -    "type": "number"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / deleted / properties / weekly_hours
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "days": {
      +        "items": {
      +          "type": "number"
      +        },
      +        "type": "array"
      +      },
      +      "end": {
      +        "type": "string"
      +      },
      +      "start": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "days",
      +      "start",
      +      "end"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / deleted / properties / window_end
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / deleted / properties / window_start
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / properties / deleted / required
      Previous value: -[
      -  "booking_page_id",
      -  "slug",
      -  "title",
      -  "description",
      -  "duration_minutes",
      -  "primary_color",
      -  "location",
      -  "weekdays",
      -  "window_start",
      -  "window_end",
      -  "is_default",
      -  "link",
      -  "created_at",
      -  "updated_at"
      -]New value: +[
      +  "booking_page_id",
      +  "slug",
      +  "title",
      +  "description",
      +  "duration_minutes",
      +  "primary_color",
      +  "calendar_view",
      +  "theme",
      +  "location",
      +  "weekly_hours",
      +  "is_default",
      +  "link",
      +  "created_at",
      +  "updated_at"
      +]
    • changedOutput schema / properties / new_default / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "booking_page_id": {
      -        "type": "string"
      -      },
      -      "created_at": {
      -        "type": "string"
      -      },
      -      "description": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "duration_minutes": {
      -        "type": "number"
      -      },
      -      "is_default": {
      -        "type": "boolean"
      -      },
      -      "link": {
      -        "type": "string"
      -      },
      -      "location": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "primary_color": {
      -        "type": "string"
      -      },
      -      "slug": {
      -        "type": "string"
      -      },
      -      "title": {
      -        "type": "string"
      -      },
      -      "updated_at": {
      -        "type": "string"
      -      },
      -      "weekdays": {
      -        "items": {
      -          "type": "number"
      -        },
      -        "type": "array"
      -      },
      -      "window_end": {
      -        "type": "string"
      -      },
      -      "window_start": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "booking_page_id",
      -      "slug",
      -      "title",
      -      "description",
      -      "duration_minutes",
      -      "primary_color",
      -      "location",
      -      "weekdays",
      -      "window_start",
      -      "window_end",
      -      "is_default",
      -      "link",
      -      "created_at",
      -      "updated_at"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "booking_page_id": {
      +        "type": "string"
      +      },
      +      "calendar_view": {
      +        "enum": [
      +          "month",
      +          "two_weeks"
      +        ],
      +        "type": "string"
      +      },
      +      "created_at": {
      +        "type": "string"
      +      },
      +      "description": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "duration_minutes": {
      +        "type": "number"
      +      },
      +      "is_default": {
      +        "type": "boolean"
      +      },
      +      "link": {
      +        "type": "string"
      +      },
      +      "location": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "primary_color": {
      +        "type": "string"
      +      },
      +      "slug": {
      +        "type": "string"
      +      },
      +      "theme": {
      +        "enum": [
      +          "dark",
      +          "light"
      +        ],
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "updated_at": {
      +        "type": "string"
      +      },
      +      "weekly_hours": {
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "days": {
      +              "items": {
      +                "type": "number"
      +              },
      +              "type": "array"
      +            },
      +            "end": {
      +              "type": "string"
      +            },
      +            "start": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "days",
      +            "start",
      +            "end"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "booking_page_id",
      +      "slug",
      +      "title",
      +      "description",
      +      "duration_minutes",
      +      "primary_color",
      +      "calendar_view",
      +      "theme",
      +      "location",
      +      "weekly_hours",
      +      "is_default",
      +      "link",
      +      "created_at",
      +      "updated_at"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds real substance on top: the public link stops working, and if the deleted page was the main page the oldest remaining page is promoted and named in the reply. It does not state whether deletion is reversible or what happens to pages with dependent content, which is the main remaining gap for a destructive operation.

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?

Four short sentences, front-loaded with the action, then the trigger, then the consequences. Nothing is repeated from the annotations or schema and every sentence carries information an agent would otherwise have to guess.

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?

For a destructive single-entity delete with an output schema and fully documented parameters, the description covers trigger, side effect on the link, and the main-page succession outcome. Only the permanence/undo question is left implicit, which is a minor but real omission for a destructive call.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter (workspace_id, booking_page_id, conversation_id, idempotency_key, workspace_scope) is documented in the schema itself. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource plus a cardinality constraint ("Delete one booking page"), which cleanly separates it from well_update_booking_page and well_list_booking_pages. It does not name those siblings explicitly, so differentiation is inferred rather than stated.

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?

"Call this when the user asks to delete a booking page they named" gives a clear triggering condition tied to a user request and an identified page. There is no when-not guidance (e.g. what to do if the page is unknown or the user means to unpublish instead), so it stops short of full routing guidance.

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