Skip to main content
Glama

mcp-notion__notion-list-session-events

Read-only

List short summaries of saved events in a Custom Agent session.

Requires Notion AI and Custom Agents access. Call this tool directly. If access is denied, follow the recovery guidance in the result. Through Royally: its server marks it read-only, so it runs straight away.

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": {
      "session_url": "<session_url>",
      "count": "<count>"
    },
    "name": "mcp-notion__notion-list-session-events"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesMaximum number of committed events to return.
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
session_urlYesUse the complete session_url returned by session tools, unchanged. Format: session://<spaceId>/<sessionId>. Shorthand session://<sessionId> and thread://<sessionId> use the connected workspace. Fully qualified URLs must refer to that workspace.
after_sequenceNoLoad the next page of events starting after this sequence number.
before_sequenceNoLoad the previous page of events ending before this sequence number.
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds valuable authorization context (Notion AI/Custom Agents access) and a denial-recovery path. Beyond that it discloses little about behavior — no note on result ordering, page size limits, or what a 'short summary' contains — and the closing 'Through Royally ... runs straight away' sentence restates the read-only annotation rather than adding new behavior.

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 prerequisite and access-denial guidance are front-loaded and earn their place, but 'Call this tool directly' and the trailing 'Through Royally: its server marks it read-only, so it runs straight away' are filler that repeats annotation state. The description also omits any pagination hint despite two cursor parameters, so the space saved isn't spent where it would help.

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

Completeness3/5

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

For a 7-parameter read tool with full schema coverage and no output schema, the definition covers access requirements and failure recovery, which is the main non-schema risk. It leaves the agent without any indication of what a returned 'short summary' looks like or how paging interacts across calls, which matters since idempotentHint is false and cursors are supplied.

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

Parameters3/5

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

Schema description coverage is 100%, including detailed guidance on session_url format and the after_sequence/before_sequence cursor semantics, so the schema carries the parameter burden and baseline 3 applies. The description adds nothing about count limits, cursor paging, or the purpose of skill/instructions_version beyond what the schema already states.

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 opens with a concrete verb and resource: 'List short summaries of saved events in a Custom Agent session,' which tells an agent this is a listing/read of session events, and 'short summaries' hints at truncated payloads versus a full event read. It does not name the closest sibling (notion-read-session-event) to clarify which one to pick, so it falls short of full sibling differentiation.

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?

It gives a real prerequisite ('Requires Notion AI and Custom Agents access') and tells the caller to invoke directly and follow recovery guidance on denial, which is useful routing information. However, it never states when to use this listing versus reading a single event or waiting on the session, and the pagination-driven usage ('load the next page') is only visible in the schema, not the prose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources