Skip to main content
Glama
marlonluo2018

Microsoft Graph MCP Server

search_events

Search Microsoft 365 calendar events by subject or organizer name. List events within a time range using keywords or time-based filters.

Instructions

Search or list calendar events by keywords. Returns matching events with summary information. If no query is provided, lists events within the specified time range. All time parameters use your local timezone. When using time_range, the response includes a user-friendly display string (e.g., 'Today', 'This Week', 'This Month'). Returns: {success: boolean, events: array, count: integer, date_range: string, timezone: string}. Note: Subject search uses exact substring matching, organizer search uses fuzzy matching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query. For 'subject': event title text. For 'organizer': organizer name. Optional - if not provided, lists events within the time range
end_dateNoEnd date in your local timezone (e.g., '2024-12-31' or '2024-12-31T23:59') (optional)
start_dateNoStart date in your local timezone (e.g., '2024-01-01' or '2024-01-01T14:30') (optional)
time_rangeNoTime range type (case-insensitive, optional, in your local timezone). Accepted values: 'today', 'tomorrow', 'this_week', 'next_week', 'this_month', 'next_month' (any case). If provided, overrides start_date and end_date. Returns a user-friendly display string in the response. Examples: 'today', 'Today', 'THIS_WEEK', 'Next_Month'.
search_typeNoField to search in (optional). Options: 'subject' (search by event title with exact substring matching), 'organizer' (search by organizer name/email with fuzzy matching). Default: 'subject'
Behavior4/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 discloses exact substring matching for subject, fuzzy matching for organizer, timezone handling, time_range override, and return format. This gives sufficient behavioral transparency, though rate limits or idempotency are not mentioned.

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 5-6 sentences, front-loaded with purpose, then behavior, return format, and a note. Every sentence adds value; no fluff or repetition.

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 (5 parameters, no output schema), the description comprehensively covers behavior, search modes, time handling, and return fields. It is complete enough for an agent to use the tool correctly.

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 coverage is 100%, baseline 3. The description adds context: time_range overrides start/end date, search_type defaults to subject, and provides specifics on matching behavior. This adds value beyond the schema.

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 'search or list calendar events by keywords' and explains the difference with and without a query. It differentiates between subject and organizer searches, but does not explicitly distinguish from sibling tools like browse_events.

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 provides context for when to use search vs list (with/without query) and mentions timezone and time_range. However, it does not tell when not to use this tool or suggest alternatives like get_event_detail for detailed info.

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/marlonluo2018/microsoft_graph_mcp_server'

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