Skip to main content
Glama
dipseth

google-workspace-unlimited

Bulk Calendar Operations

bulk_calendar_operations
Destructive

Perform bulk operations like delete, list, or export on calendar events filtered by date range, title, location, or attendee.

Instructions

Perform bulk operations on calendar events with filters (date range, title pattern, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoIf True, only preview what would be affected without making changes
time_maxNoEnd of time range in RFC3339 format (e.g., '2024-12-31T23:59:59Z')
time_minNoStart of time range in RFC3339 format (e.g., '2024-01-01T00:00:00Z'). Defaults to 30 days ago if not specified
operationYesOperation to perform
calendar_idNoCalendar ID to operate onprimary
max_resultsNoMaximum number of events to process
title_patternNoRegex pattern to match event titles (case-insensitive)
attendee_emailNoFilter events by specific attendee email address
location_patternNoRegex pattern to match event locations (case-insensitive)
user_google_emailNoThe user's Google email address for Calendar access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
dryRunYes
filtersYes
messageYes
resultsYes
successYes
operationYes
userEmailYes
calendarIdYes
totalFoundYes
totalMatchedYes
totalProcessedYes
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds little beyond 'bulk operations'; it does not highlight the dry_run safety feature or other behavioral traits.

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?

One sentence with clear purpose and key filters listed, front-loaded. Could include the allowed operations (delete, list, export) for brevity without clutter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, description does not need return details, but lacks context on bulk behavior limits or atomicity. Adequate but not rich.

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 schema fully documents parameters. The description only adds generic filter mention, not enhancing meaning beyond the schema.

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?

The description clearly states the tool performs bulk operations on calendar events with filters, which distinguishes it from single-event siblings like create_event or delete_event.

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 implies bulk use but does not explicitly state when to use this tool versus individual operations, nor does it mention alternatives or exclusions.

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

Install Server

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/dipseth/google_workspace_fastmcp2'

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