Skip to main content
Glama

create_meet_event

Schedule Google Calendar events with integrated Google Meet video conferencing for team meetings and appointments.

Instructions

Create a new Google Calendar event with Google Meet integration

Args: summary: Event title/summary start_datetime: Start datetime in ISO format (e.g., '2024-12-25T10:00:00') end_datetime: End datetime in ISO format (e.g., '2024-12-25T11:00:00') description: Event description attendees: List of attendee emails timezone: Timezone (default: UTC) calendar_id: Calendar ID (default: primary)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes
start_datetimeYes
end_datetimeYes
descriptionNo
attendeesNo
timezoneNoUTC
calendar_idNoprimary

Implementation Reference

  • main.py:368-413 (handler)
    The primary MCP tool handler for 'create_meet_event', registered via @mcp.tool(). It processes inputs, delegates to the core GoogleCalendarTools method, handles errors, and returns a standardized JSON response.
    @mcp.tool()
    def create_meet_event(
        summary: str,
        start_datetime: str,
        end_datetime: str,
        description: str = "",
        attendees: Optional[List[str]] = None,
        timezone: str = "UTC",
        calendar_id: str = "primary"
    ) -> str:
        """
        Create a new Google Calendar event with Google Meet integration
        
        Args:
            summary: Event title/summary
            start_datetime: Start datetime in ISO format (e.g., '2024-12-25T10:00:00')
            end_datetime: End datetime in ISO format (e.g., '2024-12-25T11:00:00')
            description: Event description
            attendees: List of attendee emails
            timezone: Timezone (default: UTC)
            calendar_id: Calendar ID (default: primary)
        """
        try:
            result = GoogleCalendarTools.create_meet_event(
                NANGO_CONNECTION_ID, NANGO_INTEGRATION_ID, summary, start_datetime, end_datetime,
                description, attendees, timezone, calendar_id
            )
            
            if result:
                return json.dumps({
                    "success": True,
                    "event": result,
                    "message": "Event created successfully"
                }, indent=2)
            else:
                return json.dumps({
                    "success": False,
                    "message": "Failed to create event"
                }, indent=2)
        except Exception as e:
            logger.error(f"Error in create_meet_event: {e}")
            return json.dumps({
                "success": False,
                "error": str(e),
                "message": "Failed to create calendar event"
            }, indent=2)
  • Core helper method in GoogleCalendarTools class that performs authentication, constructs the event payload with Google Meet conference data, and inserts the event into Google Calendar using the API.
    @staticmethod
    def create_meet_event(connection_id: str, provider_config_key: str, summary: str, 
                         start_datetime: str, end_datetime: str, description: str = "", 
                         attendees: Optional[List[str]] = None, timezone: str = 'UTC',
                         calendar_id: str = 'primary') -> Optional[Dict]:
        """Create a new event in Google Calendar with Google Meet integration"""
        try:
            service = GoogleCalendarAuth.authenticate_google_calendar(connection_id, provider_config_key)
            
            if not summary:
                raise ValueError("Event summary (title) is required")
            
            event = {
                'summary': summary,
                'description': description,
                'start': {
                    'dateTime': start_datetime,
                    'timeZone': timezone,
                },
                'end': {
                    'dateTime': end_datetime,
                    'timeZone': timezone,
                }
            }
            
            # Add attendees if provided
            if attendees:
                event['attendees'] = [{'email': email} for email in attendees]
            
            # Add Google Meet conference
            event['conferenceData'] = {
                'createRequest': {
                    'requestId': f"meet-{datetime.now().strftime('%Y%m%d%H%M%S')}",
                    'conferenceSolutionKey': {
                        'type': 'hangoutsMeet'
                    }
                }
            }
            
            created_event = service.events().insert(
                calendarId=calendar_id,
                body=event,
                conferenceDataVersion=1,
                sendUpdates='all'
            ).execute()
            
            return created_event
            
        except HttpError as error:
            logger.error(f'HTTP error in create_meet_event: {error}')
            return None
        except Exception as error:
            logger.error(f'Unexpected error in create_meet_event: {error}')
            return None
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool creates events with Meet integration but doesn't disclose critical behavioral traits like whether this requires specific permissions, if it sends invitations automatically, rate limits, error conditions, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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 well-structured with a clear purpose statement followed by parameter details. Every sentence adds value, and it's appropriately sized for a 7-parameter tool. Minor room for improvement in making the purpose statement even more front-loaded.

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?

For a mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It covers parameters well but lacks critical context about behavioral outcomes, error handling, authentication requirements, and what the tool returns. The agent would be guessing about important operational aspects.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It provides clear semantic explanations for all 7 parameters beyond just their names, including format examples (ISO format), defaults (timezone: UTC, calendar_id: primary), and clarifications (e.g., 'Event title/summary'). This adds substantial value over 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 Google Calendar event') and the key feature ('with Google Meet integration'), distinguishing it from sibling tools like get_calendar_events or cancel_calendar_event which perform different operations. It precisely identifies both the verb and resource.

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?

No explicit guidance on when to use this tool versus alternatives is provided. While the purpose is clear, there's no mention of prerequisites (e.g., authentication needs), when not to use it (e.g., for read-only operations), or how it differs from other event-related tools beyond its basic function.

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/Shameerpc5029/google-calendar-mcp'

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