Skip to main content
Glama

create_booking_link

Read-only

Generate booking deep-links for an ONGOING MENTORSHIP (subscription / PricingPlan). Returns:

  • apply_url: where the user starts the subscription. Optional plan_hash pre-selects a specific plan.

  • inquiry_url: free question before committing (no booking).

  • requires_intro_call: when true, the mentor offers an intro call (free or paid – see intro_call_note). apply_url already routes the user to the scheduler first — mention the intro call when sharing it.

IMPORTANT: this tool is for ongoing mentorships only. For ONE-OFF SESSIONS, use the booking_url from get_sessions_or_services directly — those bookings go through /sessions//book/, NOT /apply/.

The user must click the link and sign in via the browser — this tool does NOT book on their behalf.

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": {
      "username": "<username>"
    },
    "name": "create_booking_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentNo
usernameYes
plan_hashNo

Output Schema

NameRequiredDescriptionDefault
errorNoError code: 'not_found' or 'rate_limit_exceeded'. Absent on success.
messageNoHuman-readable error detail.
usernameNoEchoes the requested username on a not_found error.
apply_urlNoWhere the user starts the subscription. The user must click and sign in; this tool does not book on their behalf.
next_stepNoWhat to do with the links.
inquiry_urlNoFree-question link before committing (no booking).
booking_routeNoAlways 'apply'.apply
intro_call_noteNoGuidance about the intro call (free or paid); present only when requires_intro_call is true.
requires_intro_callNoWhen true, apply_url routes to the scheduler first; mention the intro call (see intro_call_note for free vs paid).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false, openWorldHint=true), the description discloses the key behavioral fact that this tool does NOT book on the user's behalf — the user must click and sign in via browser. It also states plan_hash pre-selects a plan and that apply_url already routes through the scheduler when an intro call exists, which is non-obvious downstream behavior.

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?

Purpose is front-loaded, the return values are bulleted, and the IMPORTANT routing warning is visually separated. The return-value enumeration overlaps with the existing output schema, and the bullet indentation is uneven, but no sentence is filler.

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 three-parameter link generator with an output schema and read-only annotations, this covers the essential decision (mentorship vs one-off), the non-booking constraint, and result shape. The remaining gap is the undocumented `intent` parameter and why username is required, which would matter when constructing the 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 0%, so the description must carry the load. It explains `plan_hash` meaningfully ('optional plan_hash pre-selects a specific plan') but says nothing about `intent` or what `username` refers to (the mentor's handle vs the user's), leaving two of three parameters undocumented in both schema and description.

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 and resource: 'Generate booking deep-links for an ONGOING MENTORSHIP (subscription / PricingPlan)'. It immediately distinguishes itself from the one-off-session path by naming the sibling pattern (`booking_url` from get_sessions_or_services) and the differing URL route (/apply/ vs /sessions/<slug>/book/).

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 exclusion is given: 'this tool is for ongoing mentorships only. For ONE-OFF SESSIONS, use the `booking_url` from get_sessions_or_services directly'. It also routes the intro-call case by explaining that apply_url already goes to the scheduler and the agent should mention the intro call, which is actionable when-to-use 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