Skip to main content
Glama

Coline

Update scheduling link

update_scheduling_link
Idempotent

Changes a scheduling link: its hours, length, questions, hosts, or turns it off. Only the fields you pass change.

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": {
      "workspace": "<workspace>",
      "linkId": "<linkId>"
    },
    "name": "update_scheduling_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoThe link's address; default from the title.
titleNo
linkIdYesScheduling link id from list_scheduling_links.
isActiveNo
locationNo
timeZoneNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
bookingFlowNoinstant books straight away; proposal and poll wait for the person to pick.
descriptionNo
hostUserIdsNo
conferencingNo
routingRulesNo
embedSettingsNo
openingOptionsNo
schedulingTypeNo
durationMinutesNo
intakeQuestionsNo
availabilityRulesNoBookable hours; default the person's working hours.
bookingWindowDaysNo
bufferAfterMinutesNo
fallbackHostUserIdNo
bufferBeforeMinutesNo
slotIntervalMinutesNo
minimumNoticeMinutesNo
allowBookingOverFocusTimeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare non-destructive, idempotent mutation semantics, so the bar is lower. The description still adds real value by stating the patch behavior ('Only the fields you pass change') and noting that the link can be turned off, which prevents an agent from assuming omitted fields are cleared. It leaves out permission requirements and any side effects on existing bookings, so it is not fully complete.

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?

Two short sentences, front-loaded with the verb and resource, and the second sentence delivers the important partial-update rule. There is no filler.

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 25-parameter mutation tool with nested objects and only 20% schema description coverage, the description is too thin. It does not explain the parameter groups, the meaning of linkId versus slug and workspace, or the implications of changing hosts or availability. The output schema reduces the need to describe return values, but the input side remains under-explained.

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 20% across 25 parameters, so the description needs to compensate heavily. It names broad categories (hours, length, questions, hosts, off) that map to several fields, but it leaves the majority undocumented, including routingRules, openingOptions, embedSettings, conferencing, bookingFlow, buffers, and schedulingType.

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?

The description names a specific verb ('Changes') and resource ('a scheduling link') and enumerates the editable dimensions: hours, length, questions, hosts, and active status. It does not explicitly contrast with create_scheduling_link, delete_scheduling_link, or get_scheduling_link, but 'Changes' plus 'Only the fields you pass change' makes the update role clear enough to distinguish it in practice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: modify an existing link rather than create or delete one. However, there is no explicit when-to-use guidance, no mention of prerequisites such as the link existing or the caller needing ownership, and no routing to alternatives like create_scheduling_link when the link does not yet exist.

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