Skip to main content
Glama
aaronsb

Google Workspace MCP Server

by aaronsb

manage_calendar

Check availability and manage Google Calendar events: list schedules, view agendas, create events from natural language or details, update, delete, and check free/busy availability across calendars.

Instructions

List events, view agenda, check availability, or manage calendar events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd time (ISO 8601) — or, when allDay is true, a DATE (YYYY-MM-DD) that is the INCLUSIVE last day; the exclusive end date the Calendar API requires is computed for you. Optional for all-day events: a missing end (or one equal to start) makes a one-day event.
daysNoNumber of days ahead to show (default: today only)
meetNoAdd a Google Meet video conference link. On `update`, true adds a link and false REMOVES an existing one; omit it to leave the link as it is.
textNoNatural language event description
weekNoShow this week's events
emailYesAccount email address
queryNoFree-text search terms to filter events
startNoStart time (ISO 8601) — or a DATE (YYYY-MM-DD) when allDay is true
allDayNoWhether the event is all-day. When true, start and end are DATES (YYYY-MM-DD — an ISO datetime's date part is used) and end, if given, is the INCLUSIVE last day; the exclusive end date the Calendar API requires is computed for you. Omit it (or pass false) for a timed event with start/end as dateTime — pass false with new datetimes to convert an all-day event back to a timed one. On `update`, converting TO all-day needs only one of start/end; the other is derived from the event on record. Converting FROM all-day needs both, because the missing one would need a time of day only you can choose.
eventIdNoEvent ID
summaryNoEvent title
timeMaxNoEnd of range (ISO 8601)
timeMinNoStart of range (ISO 8601). On `list`, defaults to today.
locationNoEvent location
tomorrowNoShow tomorrow's events instead of today
attendeesNoComma-separated email addresses. On `update`, whatever you pass REPLACES the existing list — addresses you leave out are removed, and an empty string clears everyone. OMIT the parameter to leave the attendee list untouched while changing other fields. On `freebusy`, the addresses whose availability to check.
operationYeslist: upcoming events — defaults to primary calendar, use calendarId to target a specific calendar (use 'calendars' operation to discover IDs) | agenda: today's schedule at a glance (all calendars). Returns calendarId per event for follow-up get calls. | get: full event details by ID. For shared calendar events, calendarId is required (use agenda or list to discover it). | create: create a new calendar event | quickAdd: create event from natural language (e.g. 'Lunch with Alice tomorrow at noon') | update: update an existing event (patch semantics — only changed fields needed) | delete: delete an event | calendars: list all calendars the user has access to | freebusy: check availability (free/busy) for a time range. Automatically includes own calendar; add attendees to check others.
calendarIdNoCalendar ID. Use the `calendars` operation to list available IDs; required for events on shared calendars. Defaults to 'primary' on the event operations (`list`, `get`, `create`, `quickAdd`, `update`, `delete`). On `agenda`, a calendar name or ID to filter to — OMIT it to span all calendars, and do not pass 'primary', which is an API alias rather than an id agenda matches on. On `freebusy`, a comma-separated list of calendar IDs to check IN ADDITION to your own.
maxResultsNoMax events (default: 10, max: 50)
descriptionNoEvent description or notes
Install Server

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description itself must disclose behavioral traits. It only lists broad capabilities and never mentions that create/update/delete mutate data, that update uses patch semantics, that attendees are replaced, or that deleting is irreversible. Some behavioral detail appears in the parameter descriptions, but the main description does not carry the burden for an unannotated tool.

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?

The description is one short sentence with no fluff and front-loads concrete capabilities. The trailing phrase 'or manage calendar events' is redundant and generic, preventing a 5, but the overall text is concise and readable.

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?

This is a complex tool with 20 parameters, 9 operations, and no output schema, yet the schema parameter descriptions cover almost all invocation concerns: per-operation behavior, default calendars, shared-calendar requirements, patch semantics, and availability ranges. The top-level description is thin, but the definition as a whole is sufficiently complete for an agent to select and call the tool safely.

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%, so the input schema already documents all 20 parameters in detail. The description text adds no parameter-level meaning, meeting the baseline for high coverage. The schema's own descriptions are unusually rich (e.g., allDay boundary handling, attendee replacement), but that is schema content, not description-added value.

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?

The description clearly identifies the resource (calendar events, agenda, availability) and gives concrete verbs: list, view, check, manage. It is not a mere tautology, though 'manage calendar events' is broad and duplicates the tool name rather than enumerating the create/update/delete operations 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?

The description does not explicitly state when to use this tool instead of alternatives such as manage_meet or manage_tasks, but the calendar resource and availability/agenda wording imply its scope. The operation parameter descriptions provide detailed internal routing (e.g., use 'calendars' to discover IDs, 'agenda' for shared calendars), so usage guidance is partially covered within the schema rather than the top-level description.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aaronsb/google-workspace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server