Skip to main content
Glama

mcp-notion__notion-read-session-event

Read-only

Read the full visible content of one saved Custom Agent session event.

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>",
      "sequence": "<sequence>"
    },
    "name": "mcp-notion__notion-read-session-event"
  }
}

Input Schema

NameRequiredDescriptionDefault
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)
sequenceYesCommitted event sequence number to read.
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.
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.4/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 the access requirement and denial-recovery behavior, plus the qualifier 'visible' implying permission-scoped content. It says nothing about ordering guarantees, pagination, or what happens for a sequence that has not committed, which are the traits an agent would actually need here.

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?

Three short sentences, front-loaded with the action, then prerequisites, then failure handling. The closing sentence about Royally's read-only marking is host-specific filler that repeats what the annotations already assert, so it does not fully earn its place.

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?

With no output schema, the description carries more burden, and 'full visible content' only loosely signals the return shape. Access requirements and error handling are covered, but the relationship to the sequence-based session tools and the expected event structure are not, leaving it adequate rather than complete.

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%, and each parameter (session_url format, sequence, skill, site_id, instructions_version) is documented in the schema itself. The description adds no extra syntax or constraints beyond the prose 'one saved ... event'. Baseline 3 is appropriate when the schema carries the semantics.

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 gives a specific verb and resource: 'Read the full visible content of one saved Custom Agent session event.' That is clear enough to know the tool returns a single event body. It does not, however, name the sibling it contrasts with (e.g. notion-list-session-events for enumerating events), so the differentiation is left implicit.

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 states prerequisites ('Requires Notion AI and Custom Agents access') and an error path ('If access is denied, follow the recovery guidance in the result'), which is real guidance. It never says when to pick this over list-session-events or get-session-status, so the usage context is only implied.

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