Skip to main content
Glama

list_calendar_events

Retrieve upcoming Google Calendar events by specifying time ranges, search terms, or result limits to manage your schedule.

Instructions

    List events from the user's Google Calendar.
    
    This tool retrieves a list of upcoming events from the user's calendar.
    
    Prerequisites:
    - The user must be authenticated with Google Calendar access
    
    Args:
        max_results (int, optional): Maximum number of events to return. Defaults to 10.
        time_min (str, optional): Start time for the search in ISO format or natural language.
                                 Defaults to now.
        time_max (str, optional): End time for the search in ISO format or natural language.
                                 Defaults to unlimited.
        query (str, optional): Free text search terms to find events that match.
        
    Returns:
        Dict[str, Any]: The list of events including:
            - events: List of calendar events with details and links
            - next_page_token: Token for pagination (if applicable)
            
    Example usage:
    1. List upcoming events:
       list_calendar_events()
       
    2. List events for a specific time range:
       list_calendar_events(time_min="tomorrow", time_max="tomorrow at 11:59pm")
       
    3. Search for specific events:
       list_calendar_events(query="meeting")
       
    Important:
    - Always include the event_link when discussing specific events with the user
    - The event_link allows users to directly access their events in Google Calendar
    - When listing multiple events, include the event_link for each event
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNo
time_minNo
time_maxNo
queryNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: authentication prerequisites, pagination behavior (via 'next_page_token'), and output structure (list of events with details and links). It also includes important usage notes about including 'event_link' for user access. It does not mention rate limits or error handling, but covers essential operational context.

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

Conciseness3/5

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

The description is well-structured with sections (Prerequisites, Args, Returns, Example usage, Important), but it is verbose with repetitive elements (e.g., restating tool name in examples) and overly detailed usage notes that could be condensed. Every sentence adds value, but efficiency could be improved by trimming redundancy.

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?

For a tool with no annotations, no output schema, and 4 parameters, the description is largely complete: it covers purpose, prerequisites, parameters, returns, examples, and important behavioral notes. It lacks explicit error handling or rate limit info, but given the context signals, it provides sufficient guidance for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given 0% schema description coverage, the description fully compensates by detailing all four parameters: 'max_results' (defaults, purpose), 'time_min' and 'time_max' (formats, defaults, purpose), and 'query' (purpose). It adds meaning beyond the schema by explaining usage contexts, formats (ISO or natural language), and defaults, making parameters clear and actionable.

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's purpose: 'List events from the user's Google Calendar' and 'retrieves a list of upcoming events from the user's calendar.' It uses specific verbs ('list,' 'retrieves') and identifies the resource ('Google Calendar events'), distinguishing it from siblings like 'create_calendar_event' or 'detect_events_from_email.'

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

Usage Guidelines4/5

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

The description provides clear context for usage through prerequisites (authentication required) and example scenarios (listing upcoming events, specific time ranges, searching). However, it lacks explicit guidance on when not to use this tool or direct alternatives among siblings, such as 'search_emails' for email-related events.

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/bastienchabal/gmail-mcp'

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