Skip to main content
Glama

graph_list_event_instances

Lists occurrences of a recurring calendar event within a date range, returning occurrence IDs so you can update or cancel individual instances.

Instructions

List the occurrences of a recurring event in a date range.

Pass the series master event ID from graph_list_events, then use the returned occurrence IDs to update or cancel a single occurrence.

Args: event_id: The recurring series master event ID. start_datetime: Start of the occurrence window (ISO 8601). Required by Graph. end_datetime: End of the occurrence window (ISO 8601). Required by Graph. top: Maximum number of occurrences to return (default 50, maximum 50). skip: Number of items to skip before returning results (default 0). Graph returns at most 50 per call, so page by raising skip in steps of top. compact: Whether to return only the identifying fields instead of the full record (default false). Use it to page through large collections cheaply. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list). user: Shared or delegated calendar owner address or user ID to act on. Empty targets your own calendar. Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "event_id": "<event_id>",
      "start_datetime": "<start_datetime>",
      "end_datetime": "<end_datetime>"
    },
    "name": "graph_list_event_instances"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
skipNo
userNo
compactNo
event_idYes
next_linkNo
end_datetimeYes
start_datetimeYes
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly does: it discloses the 50-item page ceiling, that next_link overrides the other paging arguments, that include_next_link changes the return shape to {items, next_link}, and that the user parameter requires delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared. It never explicitly states that the call is read-only and is arguably misleading about the top limit (description says maximum 50, schema allows up to 2^53-1).

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?

Front-loaded purpose sentence, then a usage sentence, then a structured Args block where every line adds information an agent needs for one of the nine parameters. No redundant restatement of the name or title.

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 nine-parameter tool with no annotations and no output schema, the description is unusually complete on pagination, permissions, and parameter semantics. The remaining gap is return-value shape: it hints at a 'full record' via compact but never describes what fields an occurrence carries, which matters given there is no output schema.

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?

Schema coverage is 0%, so the description must supply all meaning, and the Args block documents every one of the nine parameters: ISO 8601 formats, defaults, the paging idiom ('raise skip in steps of top'), next_link precedence, compact for cheap paging, and the permission requirement on user. This is meaningfully more than the bare typed schema provides.

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?

Specific verb plus resource: lists the occurrences (instances) of a recurring event, not events generally, and it explicitly tells the agent to obtain the series master ID from graph_list_events, which cleanly separates it from its closest sibling.

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?

Gives an explicit workflow: take the series master ID from graph_list_events, then feed the returned occurrence IDs into update or cancel for a single occurrence. It stops short of naming the specific sibling tools for those later steps or stating when to prefer viewing a whole series versus one occurrence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools