Skip to main content
Glama

create_calendar_event

Create new events in Google Calendar with details like title, time, location, attendees, and color coding.

Instructions

    Create a new event in the user's Google Calendar.
    
    This tool creates a new calendar event with the specified details.
    
    Prerequisites:
    - The user must be authenticated with Google Calendar access
    
    Args:
        summary (str): The title/summary of the event
        start_time (str): The start time of the event in ISO format (YYYY-MM-DDTHH:MM:SS) or simple date/time format ("5pm", "tomorrow 3pm")
        end_time (str, optional): The end time of the event. If not provided, you should ask the user for this information.
        description (str, optional): Description or notes for the event. If not provided, leave it blank.
        location (str, optional): Location of the event. If not provided, leave it blank.
        attendees (List[str], optional): List of email addresses of attendees. The current user will always be added automatically.
        color_name (str, optional): Color name for the event (e.g., "red", "blue", "green", "purple", "yellow", "orange")
        
    Returns:
        Dict[str, Any]: The result of the operation, including:
            - success: Whether the operation was successful
            - message: A message describing the result
            - event_id: The ID of the created event
            - event_link: Direct link to the event in Google Calendar
            - missing_info: List of missing information that should be asked from the user
            
    Example usage:
    1. Create a simple event:
       create_calendar_event(summary="Team Meeting", start_time="2023-12-01T14:00:00")
       
    2. Create a detailed event:
       create_calendar_event(
           summary="Project Kickoff",
           start_time="next monday at 10am",
           end_time="next monday at 11:30am",
           description="Initial meeting to discuss project scope",
           location="Conference Room A",
           attendees=["colleague@example.com", "manager@example.com"],
           color_id="2"
       )
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes
start_timeYes
end_timeNo
descriptionNo
locationNo
attendeesNo
color_nameNo
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 behavioral traits: it's a write operation (creates new events), requires authentication, specifies that the current user is automatically added to attendees, and indicates the tool will return missing information to ask the user. It doesn't mention rate limits or error handling, but covers the essential mutation behavior well.

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 clear sections (Prerequisites, Args, Returns, Example usage), but it's quite lengthy with detailed parameter explanations and multiple examples. Some information could be more concise, though all content appears purposeful. The front-loading is good with the core purpose stated first.

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

Completeness5/5

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

Given the complexity of a 7-parameter write operation with no annotations and no output schema, the description provides excellent completeness. It covers authentication requirements, parameter semantics, return value structure, and includes practical examples. For a mutation tool with rich parameters, this description gives the agent everything needed to invoke it correctly.

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?

The schema description coverage is 0%, so the description must fully compensate. It provides comprehensive parameter semantics beyond just names: it explains what each parameter represents, gives format examples (ISO format or natural language for start_time), specifies optional parameters and their default behaviors, and provides usage examples. This adds significant value beyond the bare 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 specific action ('Create a new event') and resource ('in the user's Google Calendar'), distinguishing it from sibling tools like 'list_calendar_events' or 'suggest_meeting_times'. The verb 'create' is unambiguous and the resource scope is well-defined.

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 about when to use this tool (for creating calendar events) and includes prerequisites (authentication with Google Calendar access). However, it doesn't explicitly state when NOT to use it or name specific alternatives among sibling tools, though the context implies it's for creation versus listing or suggesting.

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