MightyAutomation

Create a booking link

create_booking_link

Generate a shareable scheduling link — the contact (or anyone with the link) can book an appointment on the workspace calendar. Optionally bind it to a contact so the booking attaches to their record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_booking_link"
  }
}

Input Schema

Name	Required	Description
`title`	No	Link title shown to the booker (default "Call with us").
`contact_id`	No	The contact id (uuid) from find_contact / list_contacts / search_leads.
`window_end`	No	ISO 8601 — latest bookable time.
`window_start`	No	ISO 8601 — earliest bookable time.
`location_type`	No	Where the meeting happens.
`expires_in_days`	No	Days until the link stops accepting bookings.
`location_detail`	No	Location detail — phone number, address, or custom text.
`duration_minutes`	No	Slot length in minutes (default 15).

Output Schema

Name	Required	Description
`ok`	No
`url`	No
`slug`	No
`error`	No	Present only when ok is false.
`link_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, and non-idempotent. The description usefully explains *why* it is open-world — anyone with the link can book — and notes the optional contact binding that attaches the booking to a record, which is real behavioral context beyond the annotations.

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 sentences, front-loaded with the core action and followed by the single optional nuance that matters (contact binding). Zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Eight optional parameters are fully documented in the schema, an output schema exists, and annotations cover the safety profile. The description supplies the remaining conceptual piece — the link is publicly shareable and can be tied to a contact — so an agent has enough to call it correctly.

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%, with defaults and enum values documented inline (duration default 15, location_type enum, expires_in_days bounds). The description adds no parameter-level detail, 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?

States a specific verb and resource: 'Generate a shareable scheduling link' that lets a contact book on the workspace calendar. That clearly separates it from create_appointment (which books an actual slot), though no sibling is named explicitly.

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: produce a link when you want someone else to self-schedule, and optionally bind it to a contact via contact_id. No explicit when-not guidance or mention of create_appointment as the alternative when the time is already known.

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

All MightyAutomation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?