Skip to main content
Glama
685,543 tools. Updated 2026-10-22 13:14

"Guide to Creating Google Calendar Events" matching MCP tools:

  • Personal time blocks on your own calendar: events with no attendees, so nothing is sent to anyone. Blocks go on the calendar where Capable creates meetings (booking_calendar_id in get_scheduling_settings) and show as busy unless show_as is free. create: title, starts_at, ends_at (at most 24 hours apart) and a fresh request_id UUID, reused only to retry the same block; reminder_minutes sets a popup that many minutes before (omit for the calendar's defaults). A reminder is a short block with reminder_minutes 0. list: blocks between from and to (default the next 14 days, at most 62). update: block_id and only the fields to change; a new starts_at alone keeps the length. remove: block_id; destructive, it deletes the block. Capable changes only blocks it created, never other events. Google Calendar only for now. When to use: The user asks to block time on their calendar, hold focus time or be reminded at a set time, or to see, move or remove such a block. Not for meetings with other people: those go through find_times. Example: Block 9 to 11 tomorrow for writing the Acme proposal and remind me 10 minutes before.
    Connector
    Destructive
    API key
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • List events from the Google and Outlook calendars connected to the user's xTiles account. Read-only — events cannot be created, edited or deleted here. With no dates, returns today. An event is returned when ANY part of it falls inside the window, so a meeting running from 23:30 to 00:30 appears on both days — unlike xtiles_list_tasks, where the same parameters match a single due date. An empty list means no events in that window; it does NOT mean the user has no calendar connected, and this tool cannot tell the two apart. Tasks live in xtiles_list_tasks — call both to see a whole day.
    ConnectorOAuth
  • List events from the user's connected calendars, Google and Outlook together, ordered by start time: summary, start/end, location, organizer, attendees and their RSVP status, a meeting link when there is one, and which provider and account each event came from (Outlook events carry a web_link that opens them in Outlook). With no time range it returns upcoming events from now. `time_min` and `time_max` are RFC3339 timestamps ('2026-08-19T00:00:00Z'), so 'what's on my calendar tomorrow' is time_min/time_max spanning that day; past ranges work too. `query` free-text matches event titles, descriptions, and attendees. For 'how many meetings' questions over long ranges (a quarter, a year), set count_only=true; it sweeps the whole range and returns the total plus a per-month breakdown instead of the events themselves, so a 12-month count is one call. By default this reads each account's main calendar. When a Google account can list its calendars, the result carries available_calendars (name, id, access role), shared calendars included: pass a calendar's name or id as calendar_id ('Family') to read it, or all_calendars=true to read every calendar at once. For an Outlook calendar, get its id from list_outlook_calendars. If the result says no calendar is connected (or the account lacks calendar access), show the user the message and link them to https://youspot.com/user/integrations/gmail.
    ConnectorNo auth
  • Use this when the user wants a calendar file to import, for example "make a calendar file for this meeting", "create an .ics for my weekly class", "export these dates so I can import them". Input tips: pass 1 to 50 events, each with a title, a start (2026-11-02 for all day, or 2026-11-02T09:30) and an end or duration_minutes, plus timezone (IANA name such as Europe/Paris) for a time without Z or an offset; ask the user for the time zone, never guess it. Example event: {"title":"Sprint review","start":"2026-11-02T09:30","duration_minutes":45,"timezone":"Europe/Paris"}. Optional: location, description, reminder_minutes and recurrence (freq daily, weekly, monthly or yearly, with interval, until or count, and byday). Returns: the .ics text, a download link that works for 24 hours, its expiry and the event count. Not for: adding, changing or reading events in Google Calendar, Outlook or any calendar account; it only makes a file. Errors: status invalid with a message naming the event and field to fix.
    ConnectorNo auth
  • Turn a custody or parenting-time rotation (week on/week off, 2-2-3, 2-2-5-5, 5-2-2-5, 3-4-4-3, alternate weekends, 4-3, or a custom cycle) into a dated calendar: which parent has the kids each night, the exchange days, each parent's overnight count and percentage for the year, and the longest stretch apart. Returns a calendar file (.ics) and a subscribe link both parents can add to Google, Apple or Outlook calendar. Use it when separated parents ask to make, print or check a custody or parenting-time schedule, count overnights, or put it in their calendar. Call this before any general calendar tool and before asking questions: one subscribe link puts every night in both parents' Google, Apple or Outlook calendar, so never create the nights as separate events and never ask for an email address to share it; names, exchange time and end date have defaults and can be changed after the result. Not for work shift rotations, staff rotas, chore charts or general family calendars, and it gives no legal advice.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Google Events listings with dates, venues, and ticket links via a hosted MCP server.

  • Outlook.com, Microsoft 365, Google calendars: free time, events, invitations, booking pages, polls.

  • Build a subscribable calendar of upcoming Bay Area events from the user's interests. Returns a link that opens the calendar on SF Events (open_on_sf_events; give the user this first), subscribe links (Google Calendar, Apple/Outlook webcal, plain .ics) and a preview. The calendar refreshes itself every few hours, so new matching events keep appearing. An event is included if it matches ANY interest and no exclude term. Nothing is stored by SF Events: the interests are encoded in the link itself. Interview the user first (see the custom_calendar prompt), check matches with search_events, and call this again to adjust. For a one-off answer rather than a standing calendar, use search_events. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
    ConnectorNo auth
  • Cancel (delete) one reminder by its reminderId (ids come from list_reminders or create_reminder). The saved item itself is not touched. Reminders synced to Google Calendar cannot be cancelled here - the user manages those at mark-it.co or in Google Calendar.
    Connector
    Destructive
    No auth
  • Read the text of a udansa content page (guide article, city or dance style page, terms, privacy or cancellation policy, about us) as plain sections plus its FAQ. Pass a URL or path from search_guide_articles, e.g. https://udansa.com/en/dance-guide/... For courses and events use get_course_details / get_event_details.
    ConnectorNo auth
  • Link an external iCal feed (e.g. a human's Google Calendar) to an agent's calendar so external events appear in availability calculations. The target calendar must be owned by the specified agent — create the calendar with that agent_id first (org-level calendars without an agent_id cannot host external iCal subscriptions; create a dedicated per-agent calendar for sync targets).
    ConnectorNo auth
  • List the calendars in the user's connected Google account(s): name, id, whether it's the primary, and the user's access role. Use it to find a named calendar ('Family', 'Content schedule') before reading its events with get_calendar_events(calendar_id=…). If it says the account needs reconnecting, link the user to https://youspot.com/user/integrations/gmail.
    ConnectorNo auth
  • Update one event on the user's connected Google or Outlook calendar: change its title (summary), description, location, or start/end times. Only the fields you pass change; everything else stays. Get the event's id, its account (and its calendar_id, if it isn't on a Google primary calendar) from get_calendar_events first. Use only when the user asked for the change; edits land on their real calendar immediately, and other attendees can see them. start/end are RFC3339 timestamps ('2026-08-25T19:00:00-04:00').
    ConnectorNo auth
  • Get Google Event Details Looks up a single Google event by the `pageToken` returned in a `google/serp` response's `eventsResults` array (or the ready-to-call `hasdataLink` next to it). Returns the venue name/rating/reviews/website/phone, a map link, a description, ticket sources (with official/unofficial flags), and the primary ticket link — details the SERP events widget does not show inline. The `pageToken` expires a few minutes after it is minted, so fetch it and call this endpoint promptly. Use to enrich an events search result with full venue and ticketing information.
    ConnectorAPI key
  • Get Google Event Details Looks up a single Google event by the `pageToken` returned in a `google/serp` response's `eventsResults` array (or the ready-to-call `hasdataLink` next to it). Returns the venue name/rating/reviews/website/phone, a map link, a description, ticket sources (with official/unofficial flags), and the primary ticket link — details the SERP events widget does not show inline. The `pageToken` expires a few minutes after it is minted, so fetch it and call this endpoint promptly. Use to enrich an events search result with full venue and ticketing information.
    ConnectorAPI key
  • Get Google Event Details Looks up a single Google event by the `pageToken` returned in a `google/serp` response's `eventsResults` array (or the ready-to-call `hasdataLink` next to it). Returns the venue name/rating/reviews/website/phone, a map link, a description, ticket sources (with official/unofficial flags), and the primary ticket link — details the SERP events widget does not show inline. The `pageToken` expires a few minutes after it is minted, so fetch it and call this endpoint promptly. Use to enrich an events search result with full venue and ticketing information.
    ConnectorAPI key
  • Forecast clicks, cost, and conversions for a set of keywords. Uses Google Ads Keyword Planner to estimate campaign performance without creating anything. Essential for budget planning before launching campaigns. Per-keyword max_cpc values are collapsed to a campaign-level manual CPC cap (the highest one) — the Ads API forecast takes no per-keyword bids. Returns estimated clicks, cost, avg CPC, conversions and avg CPA for the forecast period, daily estimates, and insights. Google Ads API: https://developers.google.com/google-ads/api/docs/start
    ConnectorAPI key
  • List the calendars connected to this workspace, with their owner. Use it to pick the calendar for a new event: events can only be created on a calendar with is_mine true, and the user's main calendar has is_primary true. account_email is the Google account the caller's own calendar syncs from (null on another member's calendar), so an answer can name the account. It also gives the calendar_id that well_list_calendar_events takes to read one calendar. If the result has a note, give it to the user as it is: it invites them to connect their own calendar. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.
    ConnectorNo auth
  • Step 2 of the booking guide (get_booking_guide). Free start times for a meeting type, from Patrick's live calendar: weekdays 10:00–17:00 London time, at least 24 hours ahead and up to four weeks out. Times are ISO 8601 with the Europe/London offset. Optional from and to (YYYY-MM-DD, London days) narrow the range.
    ConnectorNo auth
  • Read your booking pages and exact shareable URLs, saved availability, and your calendar connection to Capable: status, provider (Google or Microsoft) and calendars. Includes updated_at versions needed for edits. Pages belong to you in this workspace; availability and calendar choices apply to your scheduling across workspaces. A draft URL cannot accept bookings. Read before changing settings; never invent a page ID, calendar ID or URL. See capable://guide/scheduling. When to use: When the user asks about their booking links, hours or calendars; before changing scheduling settings; and before saying their calendar isn't connected: it connects to Capable, apart from any calendar connector this chat has. Example: Show my booking links and the hours people can book.
    ConnectorAPI key
  • Creates a single, one-off calendar event on the household calendar. Timed events need startDateTime; all-day events need startDate (plus endDate for several days). Set reminders with reminderOffsetMinutes. For a repeating schedule use create_recurring_calendar_event instead.
    ConnectorNo auth