Skip to main content
Glama
187,347 tools. Last updated 2026-06-10 08:04

"Using Google Calendar for scheduling and organization" matching MCP tools:

  • Creates a new display directly within an organization WITHOUT pairing it to physical hardware. The display starts offline and uncoupled. For physical screens, ALWAYS prefer pair_by_code instead — it creates and pairs in one step. Use create_org_display only for administrative pre-provisioning when the screen is not yet available. The display is owned by the organization, not by a personal user. Requires admin scope and manager or higher role in the organization. The organization must have available licenses (use allocate_licenses first if needed).
    Connector
  • List all active webhook endpoints for the organization. Each endpoint shows its URL, enabled state, and optional domain restriction.
    Connector
  • Returns a URL the user should open in their browser to connect a calendar. Google Calendar is supported today; Microsoft and Apple are planned. The user must be signed in to checklyra.com first. Once they grant consent, Lyra stores an encrypted refresh token and the connection becomes available to other Convene tools. Requires API key authentication for the calling agent (so we know which user is asking).
    Connector
  • Lists directly accessible Google Ads customers for the configured Google Ads credentials, including descriptive names when Google returns them. Use this to discover customer IDs before running Google Ads hierarchy or reporting tools.
    Connector
  • Returns busy windows for YOU plus a set of named attendees from your Lyra contacts, within a time window. For each attendee you provide, the tool looks up whether their Lyra profile has a connected Google calendar; if so, their busy blocks contribute to the aggregated suggested_free_intervals. If not (or if they're not a linked Lyra profile), they're marked requires_manual_confirm: true so you know to ask them directly. Cap of 8 attendees per call. Privacy: per-attendee busy time ranges are returned, never event titles or summaries. Use this when you need to find a time that works for several people at once. Requires an active Google calendar connection on your own Lyra account and API key authentication.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • User-facing render tool for Google Ads visual weekly reports. Use this directly for prompts like 'show me a Google Ads report', 'generate a Google Ads dashboard', or 'show 7/30/90-day Google Ads performance'. Do not first call google_ads_get_weekly_group_report unless you already need raw data for a non-visual answer; when this visual report renders, keep any assistant text to a brief confirmation.
    Connector
  • Manage third-party integrations for a Butterbase app (e.g., Gmail, Slack, Google Calendar). Actions: - "configure": Enable or manage a third-party integration toolkit for an app - "disable": Disable a configured integration toolkit - "list_available": List available integrations that can be enabled (curated or full catalog) - "list_connected": List connected integration accounts for an app - "list_tools": List available tool actions for connected integrations - "execute_action": Execute a tool action on a connected integration (e.g., send email, create event) Parameters by action: configure: { app_id, action: "configure", toolkit, scopes?, display_name? } disable: { app_id, action: "disable", toolkit } list_available: { app_id, action: "list_available", search? } list_connected: { app_id, action: "list_connected" } list_tools: { app_id, action: "list_tools", toolkit? } execute_action: { app_id, action: "execute_action", tool_name, params?, user_id? } Curated toolkits (first-class support): gmail, google-calendar, slack, google-sheets, notion, github, hubspot, outlook, google-drive, discord Example — configure: Input: { app_id: "app_abc123", action: "configure", toolkit: "gmail", scopes: ["gmail.send"] } Output: { id: "...", toolkit_slug: "gmail", enabled: true } Example — list_available: Input: { app_id: "app_abc123", action: "list_available" } Output: { integrations: [{ toolkit: "gmail", displayName: "Gmail", curated: true }, ...] } Example — list_connected: Input: { app_id: "app_abc123", action: "list_connected" } Output: { connections: [{ toolkit_slug: "gmail", status: "active", connected_at: "..." }, ...] } Example — list_tools: Input: { app_id: "app_abc123", action: "list_tools", toolkit: "gmail" } Output: { tools: [{ name: "GMAIL_SEND_EMAIL", description: "Send an email", parameters: {...} }, ...] } Example — execute_action (send email): Input: { app_id: "app_abc123", action: "execute_action", tool_name: "GMAIL_SEND_EMAIL", params: { to: "user@example.com", subject: "Hello", body: "World" } } Output: { successful: true, data: { messageId: "..." } } Common errors: - INTEGRATIONS_NOT_CONFIGURED: Integration API key not set - INTEGRATIONS_NOT_CONNECTED: User hasn't connected this integration - INTEGRATIONS_EXECUTION_FAILED: Integration tool execution failed - RESOURCE_NOT_FOUND: App doesn't exist
    Connector
  • Fetch complete details for a single organization (company, government entity, holding company) by canonical Scrutica ID. Returns: legal name, country of HQ, organization type, parent / subsidiary references, supply-chain edge counts. Use scrutica_query_export_controls for BIS designation details. Use scrutica_get_supply_chain for full edge graphs.
    Connector
  • Check remaining credits for the organization. Shows subscription credits, purchased credit packs, and total available credits.
    Connector
  • Returns busy windows from YOUR connected Google calendar within a time window, plus free intervals of at least the requested minimum length. Use this to check your own availability before scheduling anything — gatherings, calls, anything. The 'busy' result is sourced directly from your Google calendar's freeBusy API; no event titles or details are returned, only the time ranges. Requires an active Google calendar connection (call lyra_connect_calendar first if you don't have one) and API key authentication. Returns a clear error if no calendar is connected.
    Connector
  • Get the current Calendly user for the supplied token. Returns the user URI and organization URI — call this FIRST, since list_scheduled_events and list_event_types require a user or organization URI.
    Connector
  • Search GBIF datasets by keyword, type, country, or publishing organization. Returns dataset title, description, license, record count, and DOI. Use to find the source dataset behind a set of records, or to explore what data collections are available for a taxon, country, or organization.
    Connector
  • Returns all French national public holidays for a given year as a structured list. Each holiday includes { date: 'YYYY-MM-DD', name: string, name_en: string }. Returns 11 mandatory holidays defined by French law. Easter-dependent holidays (Easter Monday, Ascension Thursday, Whit Monday) are dynamically calculated for the requested year using the Anonymous Gregorian algorithm. Use when calculating French business deadlines, delivery dates, or scheduling tasks that must avoid non-working days in France.
    Connector
  • Returns Mexican national public holidays for any given year. Use this tool when calculating delivery dates, scheduling appointments, or any task requiring knowledge of non-working days in Mexico. Returns all national holidays with dates in YYYY-MM-DD format and names in both Spanish and English. Note: some Mexican holidays fall on the nearest Monday (puente) — the dates returned are the fixed calendar dates as established by law.
    Connector
  • Advanced expert tool that runs a bounded, validated Google Ads search over an approved resource using an allowlisted field set instead of raw GAQL. Supports criteria/settings exports for campaign bidding, targeting vs observation settings, audience bid modifiers, device/daypart/location bid adjustments, and RSA asset pinning/performance. Prefer higher-level workflow tools for reporting, diagnostics, and user-facing analysis prompts.
    Connector
  • List bookable event types (meeting templates). Requires a user URI OR an organization URI (get them from current_user). Returns event type URIs, names, durations, scheduling URLs, and active state.
    Connector
  • Full pipeline processing for a new lead: AI analysis → auto-quote from service catalog → job creation → Google Calendar sync → customer SMS → team Slack/Discord notification. The 'one-tap' lead processing pipeline.
    Connector
  • Get the name, organization, country, and description for an Autonomous System number. Lightweight version of as_whois.
    Connector