Capture a screenshot of the active Notion page to verify layout or diagrams. Use it when you need a visual check of page rendering without leaving your workspace.
Screenshot of the active Notion page (to check layout/diagrams).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page URL or id. Default: the active Notion tab. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not disclose what the tool returns (image blob, file path, base64), whether it captures the viewport or full page, whether the Notion app must be focused/foreground, or whether it fails on pages not currently open — all critical for a screenshot tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence, front-loaded with what the tool produces, with the purpose in parentheses. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no annotations and no output schema, the description omits the most decision-relevant facts: return format/where the screenshot lands, capture scope, and any focus/window prerequisites. An agent cannot predict the result shape from this definition alone.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one optional parameter with 100% schema coverage, so the schema already explains the URL/id and the default to the active tab. The description's 'active Notion page' phrasing is consistent with that default but adds no new semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Screenshot of the active Notion page') and adds the intent (checking layout/diagrams), which is far more informative than the sibling names notion_read/notion_outline. It doesn't explicitly contrast itself with those siblings, but the output type (image) makes it naturally distinguishable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The parenthetical '(to check layout/diagrams)' implies the use case — visual verification rather than content extraction — but it never says when to prefer this over notion_read or notion_outline, nor any preconditions (e.g., page must be open/visible).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.