Skip to main content
Glama
ricleedo

Google Services MCP Server

by ricleedo

calendar-list-events

Retrieve calendar events with filters for time range, recurrence, and sorting to manage schedules and track appointments.

Instructions

List calendar events with optional filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendarIdNoCalendar ID - Available options: 'primary' (Primary Calendar)primary
timeMinNoLower bound for event start time (ISO format)
timeMaxNoUpper bound for event start time (ISO format)
maxResultsNoMaximum number of events to return
singleEventsNoWhether to expand recurring events
orderByNoOrder of eventsstartTime

Implementation Reference

  • The handler function for listing calendar events. Queries Google Calendar API with provided filters, maps the response, formats as markdown, and returns in MCP format.
    export async function listEvents(
      params: z.infer<ReturnType<typeof listEventsSchema>>
    ) {
      try {
        const auth = createCalendarAuth();
        const calendar = google.calendar({ version: "v3", auth });
    
        const listParams: any = {
          calendarId: params.calendarId,
          maxResults: params.maxResults,
          singleEvents: params.singleEvents,
          orderBy: params.orderBy,
        };
    
        if (params.timeMin) listParams.timeMin = params.timeMin;
        if (params.timeMax) listParams.timeMax = params.timeMax;
    
        // If no timeMin is specified, default to current time
        if (!params.timeMin) {
          listParams.timeMin = new Date().toISOString();
        }
    
        const response = await calendar.events.list(listParams);
    
        const events = response.data.items?.map((event) => ({
          id: event.id,
          summary: event.summary,
          description: event.description,
          location: event.location,
          start: event.start,
          end: event.end,
          attendees: event.attendees?.map((a) => ({
            email: a.email,
            responseStatus: a.responseStatus,
          })),
          htmlLink: event.htmlLink,
          status: event.status,
          created: event.created,
          updated: event.updated,
        }));
    
        return {
          content: [
            {
              type: "text" as const,
              text: formatEventListToMarkdown(events || [], events?.length || 0),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error listing events: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the listEvents tool, including calendarId, time filters, maxResults, etc.
    export const listEventsSchema = () =>
      z.object({
        calendarId: z
          .string()
          .default("primary")
          .describe(getCalendarDescription()),
        timeMin: z
          .string()
          .optional()
          .describe("Lower bound for event start time (ISO format)"),
        timeMax: z
          .string()
          .optional()
          .describe("Upper bound for event start time (ISO format)"),
        maxResults: z
          .number()
          .min(1)
          .max(250)
          .default(10)
          .describe("Maximum number of events to return"),
        singleEvents: z
          .boolean()
          .default(true)
          .describe("Whether to expand recurring events"),
        orderBy: z
          .enum(["startTime", "updated"])
          .default("startTime")
          .describe("Order of events"),
      });
  • src/index.ts:224-231 (registration)
    Registers the 'calendar-list-events' tool with the MCP server, using listEventsSchema and listEvents handler.
    server.tool(
      "calendar-list-events",
      "List calendar events with optional filters",
      listEventsSchema().shape,
      async (params) => {
        return await listEvents(params);
      }
    );
  • Helper function to format the list of events into a readable markdown list, used by the listEvents handler.
    function formatEventListToMarkdown(events: any[], totalResults: number): string {
      if (!events.length) return "# No Upcoming Events\n\nNo events found in the specified time range.";
      
      let markdown = `# Upcoming Events (${totalResults})\n\n`;
      
      events.forEach((event, index) => {
        const startDate = event.start?.dateTime ? new Date(event.start.dateTime) : null;
        const endDate = event.end?.dateTime ? new Date(event.end.dateTime) : null;
        
        markdown += `## ${index + 1}. ${event.summary || 'Untitled Event'}\n`;
        
        if (startDate) {
          if (endDate && startDate.toDateString() === endDate.toDateString()) {
            // Same day event
            markdown += `When: ${startDate.toLocaleDateString()} ${startDate.toLocaleTimeString()} - ${endDate.toLocaleTimeString()}  \n`;
          } else {
            markdown += `Start: ${startDate.toLocaleString()}  \n`;
            if (endDate) markdown += `End: ${endDate.toLocaleString()}  \n`;
          }
        }
        
        if (event.location) markdown += `Location: ${event.location}  \n`;
        if (event.description) markdown += `Description: ${event.description}  \n`;
        if (event.attendees && event.attendees.length > 0) {
          markdown += `Attendees: ${event.attendees.length} people  \n`;
        }
        if (event.id) markdown += `ID: \`${event.id}\`  \n`;
        
        markdown += `\n---\n\n`;
      });
      
      return markdown;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a list operation with filters but doesn't mention pagination behavior, rate limits, authentication requirements, or what happens with large result sets. For a read operation with 6 parameters, this leaves significant gaps in understanding how the tool behaves beyond basic functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that communicates the core functionality without unnecessary words. It's appropriately sized for a list operation and front-loads the essential information.

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

Completeness2/5

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

Given the tool has 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address what the return format looks like, how results are structured, whether there's pagination for large result sets, or any error conditions. For a list operation with multiple filtering options, more context is needed.

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?

The description mentions 'optional filters' which aligns with the schema's parameters, but adds no specific semantic meaning beyond what the 100% schema description coverage already provides. The schema thoroughly documents each parameter's purpose, format, defaults, and constraints, making the description's contribution minimal.

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 states the verb ('List') and resource ('calendar events'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'calendar-list-calendars' beyond mentioning 'events' versus 'calendars', which is a minor distinction but not explicitly called out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions 'optional filters' but provides no guidance on when to use this tool versus alternatives like 'calendar-get-event' for single events or 'calendar-list-calendars' for listing calendars. There's no explicit when/when-not context or prerequisite information.

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/ricleedo/Google-Service-MCP'

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