Meetbot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEETBOT_AUTH_TOKEN | Yes | Your Meet.bot API bearer token for authentication. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_scheduling_pagesB | Get all scheduling pages for the authenticated user |
| get_page_infoC | Get information about a specific scheduling page |
| get_available_slotsB | Get available booking slots for a scheduling page |
| book_meetingC | Book a new meeting slot |
| health_checkA | Check if the Meet.bot API client is properly configured and can connect |
| list_webhooksA | List the authenticated user's outbound booking webhooks (fired on booking_received, booking_rescheduled and booking_cancelled) |
| set_webhookA | Create or update an outbound booking webhook. Omit id to create (webhook_url required); pass id to update. Meet.bot POSTs a JWT-signed (HS256) JSON payload to the URL on each booking event. |
| delete_webhookB | Delete one of the authenticated user's webhooks by id |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct area: scheduling pages (list, details, slots), booking, webhooks (list, set, delete), and a health check. No overlapping purposes; agents can easily distinguish.
All tools follow snake_case and a consistent verb_noun pattern (e.g., book_meeting, delete_webhook, get_available_slots). Even health_check fits the pattern as a common compound noun.
8 tools cover the core functionality of scheduling and webhook management. The count is well-scoped for the server's purpose—neither too few nor excessive.
The tool set lacks any post-booking management: there are no tools to update, cancel, or list bookings. While webhooks handle events, agents cannot interact with existing bookings, which is a notable gap.