Notion

Retrieves details about a Notion entity (page, database, or data source) by URL or ID. Provide URL or ID in id parameter. Make multiple calls to fetch multiple entities. Pages use enhanced Markdown format. For the complete specification, fetch the MCP resource at notion://docs/enhanced-markdown-spec. Databases return all data sources (collections). Each data source has a unique ID shown in <data-source url="collection://..."> tags. You can pass a data source ID directly to this tool to fetch details about that specific data source, including its schema and properties. Use data source IDs with update_data_source and query_data_sources tools. Multi-source databases (e.g., with linked sources) will show multiple data sources. Set include_discussions to true to see discussion counts and inline discussion markers that correlate with the get_comments tool. The page output will include a <page-discussions> summary tag with discussion count, preview snippets, and discussion:// URLs that match the discussion IDs returned by get_comments. <example>{"id": "https://notion.so/workspace/Page-a1b2c3d4e5f67890"}</example> <example>{"id": "12345678-90ab-cdef-1234-567890abcdef"}</example> <example>{"id": "https://myspace.notion.site/Page-Title-abc123def456"}</example> <example>{"id": "page-uuid", "include_discussions": true}</example> <example>{"id": "collection://12345678-90ab-cdef-1234-567890abcdef"}</example>

Add a comment to a page or specific content. Creates a new comment. Provide page_id to identify the page, then choose ONE targeting mode:

• page_id alone: Page-level comment on the entire page
• page_id + selection_with_ellipsis: Comment on specific block content
• discussion_id: Reply to an existing discussion thread (page_id is still required)

Provide exactly one content format:

• markdown: Preferred. Inline Notion-flavored Markdown for comment text. For exact syntax, fetch notion://docs/enhanced-markdown-spec and use only the Rich text types and Mentions syntax that comments support. Comments support inline formatting (bold, italic, strikethrough, underline, code, links), inline math using $Equation$, and user/page/database/date mention tags such as <mention-date start="YYYY-MM-DD"/>. Do not use UI shortcuts like @today, @name, [[page]], or autocomplete-style emoji syntax; those are editor affordances, not markdown syntax. Mention tags must include a real url where required by the spec. Block-level Markdown such as headings, lists, tables, blockquotes, and fenced code blocks is stored as plain comment text rather than rendered as blocks.
• rich_text: Array of rich text objects.

For content targeting, use selection_with_ellipsis with ~10 chars from start and end: "

Section Ti...tle content"

<example description="Page-level comment"> {"page_id": "uuid", "markdown": "Comment with important context."} </example> <example description="Comment on specific content"> {"page_id": "uuid", "selection_with_ellipsis": "

Meeting No...es heading",

"markdown": "Comment on this section."} </example> <example description="Reply to discussion"> {"page_id": "uuid", "discussion_id": "discussion://pageId/blockId/discussionId", "markdown": "Reply with [context](https://example.com)."} </example>

Creates a new Notion database using SQL DDL syntax. If no title property provided, "Name" is auto-added. Returns Markdown with schema, SQLite definition, and data source ID in <data-source> tag for use with update_data_source and query_data_sources tools. The schema param accepts a CREATE TABLE statement defining columns. Type syntax:

• Simple: TITLE, RICH_TEXT, DATE, PEOPLE, CHECKBOX, URL, EMAIL, PHONE_NUMBER, STATUS, FILES
• SELECT('opt':color, ...) / MULTI_SELECT('opt':color, ...)
• NUMBER [FORMAT 'dollar'] / FORMULA('expression')
• RELATION('data_source_id') — one-way relation
• RELATION('data_source_id', DUAL) — two-way relation
• RELATION('data_source_id', DUAL 'synced_name') — two-way with synced property name
• RELATION('data_source_id', DUAL 'synced_name' 'synced_id') — two-way with synced name and ID (for self-relations)
• ROLLUP('rel_prop', 'target_prop', 'function')
• UNIQUE_ID [PREFIX 'X'] / CREATED_TIME / LAST_EDITED_TIME
• Any column: COMMENT 'description text' Colors: default, gray, brown, orange, yellow, green, blue, purple, pink, red

<example description="Minimal">{"schema": "CREATE TABLE ("Name" TITLE)"}</example> <example description="Task DB">{"title": "Tasks", "schema": "CREATE TABLE ("Task Name" TITLE, "Status" SELECT('To Do':red, 'Done':green), "Due Date" DATE)"}</example> <example description="With parent and options">{"parent": {"page_id": "f336d0bc-b841-465b-8045-024475c079dd"}, "title": "Projects", "schema": "CREATE TABLE ("Name" TITLE, "Budget" NUMBER FORMAT 'dollar', "Tags" MULTI_SELECT('eng':blue, 'design':pink), "Task ID" UNIQUE_ID PREFIX 'PRJ')"}</example> <example description="Self-relation (two-step: create database first, then use its data source ID with update_data_source to add self-relations)">{"title": "Tasks", "schema": "CREATE TABLE ("Name" TITLE, "Parent" RELATION('ds_id', DUAL 'Children' 'children'), "Children" RELATION('ds_id', DUAL 'Parent' 'parent'))"}</example>

Overview

Creates one or more Notion pages, with the specified properties and content.

Parent

All pages created with a single call to this tool will have the same parent. The parent can be a Notion page ("page_id") or data source ("data_source_id"). If the parent is omitted, the pages are created as standalone, workspace-level private pages, and the person that created them can organize them later as they see fit. If you have a database URL, ALWAYS pass it to the "fetch" tool first to get the schema and URLs of each data source under the database. You can't use the "database_id" parent type if the database has more than one data source, so you'll need to identify which "data_source_id" to use based on the situation and the results from the fetch tool (data source URLs look like collection://<data_source_id>). If you know the pages should be created under a data source, do NOT use the database ID or URL under the "page_id" parameter; "page_id" is only for regular, non-database pages.

Content

Notion page content is a string in Notion-flavored Markdown format. Don't include the page title at the top of the page's content. Only include it under "properties". IMPORTANT: For the complete Markdown specification, always first fetch the MCP resource at notion://docs/enhanced-markdown-spec. Do NOT guess or hallucinate Markdown syntax. This spec is also applicable to other tools like update-page and fetch.

Properties

Notion page properties are a JSON map of property names to SQLite values. When creating pages in a database:

• Use the correct property names from the data source schema shown in the fetch tool results.
• Always include a title property. Data sources always have exactly one title property, but it may not be named "title", so, again, rely on the fetched data source schema.

For pages outside of a database:

• The only allowed property is "title", which is the title of the page in inline markdown format. Always include a "title" property.

IMPORTANT: Some property types require expanded formats:

• Date properties: Split into "date:{property}:start", "date:{property}:end" (optional), and "date:{property}:is_datetime" (0 or 1)
• Place properties: Split into "place:{property}:name", "place:{property}:address", "place:{property}:latitude", "place:{property}:longitude", and "place:{property}:google_place_id" (optional)
• Number properties: Use JavaScript numbers (not strings)
• Checkbox properties: Use "__YES__" for checked, "__NO__" for unchecked

Special property naming: Properties named "id" or "url" (case insensitive) must be prefixed with "userDefined:" (e.g., "userDefined:URL", "userDefined:id")

Templates

When creating a page in a database, you can apply a template to pre-populate it with content and property values. Use the "fetch" tool on a database to see available templates in the <templates> section of each data source. When using a template:

• Pass the template's ID as "template_id" in the page object.
• Do NOT include "content" when using a template, as the template provides it.
• You can still set "properties" alongside the template to override template defaults.
• Template application is asynchronous. The page is created immediately but starts blank; the template content will appear shortly after.

Icon and Cover

Each page can optionally have an icon and a cover image.

• "icon": An emoji character (e.g. "🚀"), a custom emoji by name (e.g. ":rocket_ship:"), or an external image URL. Use "none" to remove. Omit to leave unchanged.
• "cover": An external image URL. Use "none" to remove. Omit to leave unchanged.

Examples

<example description="Create a page with an icon and cover"> { "pages": [ { "properties": {"title": "My Page"}, "icon": "🚀", "cover": "https://example.com/cover.jpg" } ] } </example> <example description="Create a page from a database template"> { "parent": {"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd"}, "pages": [ { "template_id": "a5da15f6-b853-455d-8827-f906fb52db2b", "properties": { "Task Name": "New urgent bug" } } ] } </example> <example description="Create a standalone page with a title and content"> { "pages": [ { "properties": {"title": "Page title"}, "content": "

Section 1 {color="blue"}

Section 1 content <details> <summary>Toggle block</summary> Hidden content inside toggle </details>" } ] } </example> <example description="Create a page under a database's data source"> { "parent": {"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd"}, "pages": [ { "properties": { "Task Name": "Task 123", "Status": "In Progress", "Priority": 5, "Is Complete": "__YES__", "date:Due Date:start": "2024-12-25", "date:Due Date:is_datetime": 0 } } ] } </example> <example description="Create a page with an existing page as a parent"> { "parent": {"page_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"}, "pages": [ { "properties": {"title": "Page title"}, "content": "

Section 1

Section 1 content

Section 2

Section 2 content" } ] } </example>

Create a new view on a Notion database. Exactly one of "database_id" or "parent_page_id" must be provided:

• "database_id": add a new view tab to an existing database.
• "parent_page_id": create an inline linked database view on a page that references the existing "data_source_id" (like the UI "/linked" command). The linked view block is appended to the end of the parent page.

Use "fetch" first to get the database_id, parent_page_id, and data_source_id (from <data-source> tags in the response). The caller must have edit access to the database (or parent page) and access to the data source. Supported types: table, board, list, calendar, timeline, gallery, form, chart, map, dashboard. The optional "configure" param accepts a DSL for filters, sorts, grouping, and display options. See the notion://docs/view-dsl-spec resource for full syntax. Key directives:

• FILTER "Property" = "value" — filter rows
• SORT BY "Property" ASC — sort rows
• GROUP BY "Property" — group by property (required for board views)
• CALENDAR BY "Property" — date property (required for calendar views)
• TIMELINE BY "Start" TO "End" — date range (required for timeline views)
• MAP BY "Property" — location property (required for map views)
• CHART column|bar|line|donut|number — chart type with optional AGGREGATE, COLOR, HEIGHT, SORT, STACK BY, CAPTION
• FORM CLOSE|OPEN — close/open form submissions
• FORM ANONYMOUS true|false — toggle anonymous submissions
• FORM PERMISSIONS none|reader|editor — set submission permissions
• SHOW "Prop1", "Prop2" — set visible properties
• COVER "Property" — cover image property

<example description="Table view on existing database">{"database_id": "abc123", "data_source_id": "def456", "name": "All Tasks", "type": "table"}</example> <example description="Board grouped by Status">{"database_id": "abc123", "data_source_id": "def456", "name": "Task Board", "type": "board", "configure": "GROUP BY "Status""}</example> <example description="Filtered + sorted table">{"database_id": "abc123", "data_source_id": "def456", "name": "Active", "type": "table", "configure": "FILTER "Status" = "In Progress"; SORT BY "Due Date" ASC"}</example> <example description="Calendar view">{"database_id": "abc123", "data_source_id": "def456", "name": "Calendar", "type": "calendar", "configure": "CALENDAR BY "Due Date""}</example> <example description="Dashboard">{"database_id": "abc123", "data_source_id": "def456", "name": "Overview", "type": "dashboard"}</example> <example description="Linked view on a page">{"parent_page_id": "ghi789", "data_source_id": "def456", "name": "Company tasks", "type": "table", "configure": "FILTER "Company" = "Acme""}</example>

Duplicate a Notion page. The page must be within the current workspace, and you must have permission to access it. The duplication completes asynchronously, so do not rely on the new page identified by the returned ID or URL to be populated immediately. Let the user know that the duplication is in progress and that they can check back later using the 'fetch' tool or by clicking the returned URL and viewing it in the Notion app.

Get comments and discussions from a Notion page. Returns discussions with full comment content in XML format. By default, returns page-level discussions only. Tip: Use the fetch tool with include_discussions: true first to see where discussions are anchored in the page content, then use this tool to retrieve full discussion threads. The discussion:// URLs in the fetch output match the discussion IDs returned here. Parameters:

• include_all_blocks: Include discussions on child blocks (default: false)
• include_resolved: Include resolved discussions (default: false)
• discussion_id: Fetch a specific discussion by ID or URL

<example>{"page_id": "page-uuid"}</example> <example>{"page_id": "page-uuid", "include_all_blocks": true}</example> <example>{"page_id": "page-uuid", "discussion_id": "discussion://pageId/blockId/discussionId"}</example>

Retrieves a list of teams (teamspaces) in the current workspace. Shows which teams exist, user membership status, IDs, names, and roles. Teams are returned split by membership status and limited to a maximum of 10 results. <examples> 1. List all teams (up to the limit of each type): {} 2. Search for teams by name: {"query": "engineering"} 3. Find a specific team: {"query": "Product Design"} </examples>

Retrieves a list of users in the current workspace. Shows workspace members and guests with their IDs, names, emails (if available), and types (person or bot). Supports cursor-based pagination to iterate through all users in the workspace. <examples> 1. List all users (first page): {} 2. Search for users by name or email: {"query": "john"} 3. Get next page of results: {"start_cursor": "abc123"} 4. Set custom page size: {"page_size": 20} 5. Fetch a specific user by ID: {"user_id": "00000000-0000-4000-8000-000000000000"} 6. Fetch the current user: {"user_id": "self"} </examples>

Move one or more Notion pages or databases to a new parent.

Query data from Notion databases using SQL or by specifying a view. By default, uses SQL mode to execute SQLite queries across one or more data sources. Alternatively, use view mode to execute a database view's existing filters and sorts. Prerequisites: 1. Use the "fetch" tool first to get database schema and data source URLs 2. Data source URLs are found in <data-source url="..."> tags in fetch results

SQL mode (default): Execute custom SQLite queries across one or more data sources.

• Use data source URLs as table names in your query
• Supports parameterized queries for security
• Checkbox values: use "__YES__" for checked, "__NO__" for unchecked

Examples: 1. Simple query without explicit mode (defaults to SQL): { "data": { "data_source_urls": ["collection://f336d0bc-b841-465b-8045-024475c079dd"], "query": "SELECT * FROM "collection://f336d0bc-b841-465b-8045-024475c079dd" LIMIT 10" } }

2. Query with parameters: { "data": { "mode": "sql", "data_source_urls": ["collection://abc123"], "query": "SELECT * FROM "collection://abc123" WHERE Status = ? AND Priority = ?", "params": ["In Progress", "High"] } }

3. Query checkboxes: { "data": { "data_source_urls": ["collection://def456"], "query": "SELECT * FROM "collection://def456" WHERE Completed = ?", "params": ["__YES__"] } }

View mode: Execute a specific database view's query with its filters and sorts. When the response has "has_more": true, pass its "next_cursor" as "start_cursor" in a follow-up view-mode request. Example: { "data": { "mode": "view", "view_url": "https://www.notion.so/workspace/Tasks-DB-abc123?v=def456" } } Common use cases:

• Aggregate data across databases
• Filter records by complex conditions
• Export data for analysis
• Validate data quality
• Generate reports from database content

Query the current user's meeting notes data source. Applies a filter over meeting note properties. Title keyword searching is done via filter on property "title" (e.g. string_contains). Title keyword matching is case-insensitive; capitalization does not matter. Returns up to 50 rows of matching meeting notes. Prerequisites: 1. Use the "search" tool to find people IDs if you need to filter by attendees

Query building:

• Ignore terms semantically related to meeting outputs (e.g. "summaries", "notes", "todos", "action items", "deliverables"). These signal the user wants outcomes from their meetings, not a title filter.
• For example, "what are my meeting todos?" means filter meetings and find action items — do NOT add a title filter for "todos".
• Only add a title filter when confident the user is targeting a specific meeting title (e.g. "standup", "sprint planning", "1:1 with Alice").
• Generic date phrases like "recent meetings", "latest meetings", "meetings this week", or "yesterday's meetings" should be interpreted as date range filters — never as title filters.
• If a filter returns no results, simplify to a single term. The system is lexical, so multi-word title filters may not match.
• Unless a user explicitly asks about a meeting titled with another user's name, assume they're referring to attendees or creators. Only add a title filter with a person's name as a fallback if attendee filtering returns no results.

Default behavior:

• This tool by default returns meeting notes where the current user is an attendee or creator. There is no need to add a filter for the current user.

Filterable properties:

• "title" (text) — meeting title
• "notion://meeting_notes/attendees" (person) — meeting attendees
• "created_time" (date) — when the meeting note was created
• "created_by" (person) — who created the meeting note
• "last_edited_time" (date) — when the meeting note was last edited
• "last_edited_by" (person) — who last edited the meeting note

Combinator filters use "filters" (not "operands"): { "operator": "and" | "or", "filters": [ ... ] } Date filtering (recommended default: date_is_within):

• Prefer "date_is_within" for relative windows like "past N days/weeks/months".
• Relative (common): { type: "relative", value: "the_past_week" | "the_past_month" | "this_week" }
• Relative (custom): { type: "relative", value: "custom", direction: "past" | "future", unit: "day" | "week" | "month" | "year", count: <number> }
• Exact range: { type: "exact", value: { type: "daterange", start_date: "YYYY-MM-DD", end_date: "YYYY-MM-DD" } }
• Single-date operators ("date_is", "date_is_before", "date_is_after", "date_is_on_or_before", "date_is_on_or_after"):
• Exact: { type: "exact", value: { type: "date", start_date: "YYYY-MM-DD" } }
• Relative shortcuts: today | tomorrow | yesterday | one_week_ago | one_week_from_now | one_month_ago | one_month_from_now

Title keyword filtering (OR vs AND):

• Use OR ("operator": "or") when unsure or for broad discovery.
• Use AND ("operator": "and") when the user is specific and you want to narrow results.
• Break multi-word phrases into individual terms and filter on each term separately.

Example 1: Filter meetings from the past week (relative): { "filter": { "operator": "and", "filters": [ { "property": "created_time", "filter": { "operator": "date_is_within", "value": { "type": "relative", "value": "the_past_week" } } } ] } } Example 2: Filter meetings from the past 3 days (custom relative): { "filter": { "operator": "and", "filters": [ { "property": "created_time", "filter": { "operator": "date_is_within", "value": { "type": "relative", "value": "custom", "direction": "past", "unit": "day", "count": 3 } } } ] } } Example 3: Filter meetings by exact date range: { "filter": { "operator": "and", "filters": [ { "property": "created_time", "filter": { "operator": "date_is_within", "value": { "type": "exact", "value": { "type": "daterange", "start_date": "2025-01-01", "end_date": "2025-12-31" } } } } ] } } Example 4: Filter meetings created after a specific date: { "filter": { "operator": "and", "filters": [ { "property": "created_time", "filter": { "operator": "date_is_after", "value": { "type": "exact", "value": { "type": "date", "start_date": "2025-06-01" } } } } ] } } Example 5: Filter meetings by a specific attendee (use "search" tool first to get user ID): { "filter": { "operator": "and", "filters": [ { "property": "notion://meeting_notes/attendees", "filter": { "operator": "person_contains", "value": [ { "type": "exact", "value": { "table": "notion_user", "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890" } } ] } } ] } } Example 6: Combine attendees with date range: { "filter": { "operator": "and", "filters": [ { "property": "created_time", "filter": { "operator": "date_is_on_or_after", "value": { "type": "exact", "value": { "type": "date", "start_date": "2025-01-01" } } } }, { "property": "created_time", "filter": { "operator": "date_is_on_or_before", "value": { "type": "exact", "value": { "type": "date", "start_date": "2025-01-31" } } } }, { "property": "notion://meeting_notes/attendees", "filter": { "operator": "person_contains", "value": [ { "type": "exact", "value": { "table": "notion_user", "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890" } } ] } } ] } } Example 7: Filter meetings by title content: { "filter": { "operator": "and", "filters": [ { "property": "title", "filter": { "operator": "string_contains", "value": { "type": "exact", "value": "design review" } } } ] } } Example 8: Filter meetings matching any of several title terms (using "or"): { "filter": { "operator": "or", "filters": [ { "property": "title", "filter": { "operator": "string_contains", "value": { "type": "exact", "value": "standup" } } }, { "property": "title", "filter": { "operator": "string_contains", "value": { "type": "exact", "value": "sync" } } } ] } }

Update a Notion data source's schema, title, or attributes using SQL DDL statements. Returns Markdown showing updated structure and schema. Accepts a data source ID (collection ID from fetch response's <data-source> tag) or a single-source database ID. Multi-source databases require the specific data source ID. The statements param accepts semicolon-separated DDL statements:

• ADD COLUMN "Name" <type> - add a new property
• DROP COLUMN "Name" - remove a property
• RENAME COLUMN "Old" TO "New" - rename a property
• ALTER COLUMN "Name" SET <type> - change type/options

Same type syntax as create_database. Key types:

• SELECT('opt':color, ...) / MULTI_SELECT('opt':color, ...)
• NUMBER [FORMAT 'dollar'] / FORMULA('expression')
• RELATION('ds_id') / RELATION('ds_id', DUAL) / RELATION('ds_id', DUAL 'synced_name' 'synced_id')
• ROLLUP('rel_prop', 'target_prop', 'function') / UNIQUE_ID [PREFIX 'X']
• Simple: TITLE, RICH_TEXT, DATE, PEOPLE, CHECKBOX, URL, EMAIL, PHONE_NUMBER, STATUS, FILES

<example description="Add properties">{"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd", "statements": "ADD COLUMN "Priority" SELECT('High':red, 'Medium':yellow, 'Low':green); ADD COLUMN "Due Date" DATE"}</example> <example description="Rename property">{"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd", "statements": "RENAME COLUMN "Status" TO "Project Status""}</example> <example description="Remove property">{"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd", "statements": "DROP COLUMN "Old Property""}</example> <example description="Add self-relation">{"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd", "statements": "ADD COLUMN "Parent" RELATION('f336d0bc-b841-465b-8045-024475c079dd', DUAL 'Children' 'children'); ADD COLUMN "Children" RELATION('f336d0bc-b841-465b-8045-024475c079dd', DUAL 'Parent' 'parent')"}</example> <example description="Update title">{"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd", "title": "Project Tracker 2024"}</example> <example description="Trash data source">{"data_source_id": "f336d0bc-b841-465b-8045-024475c079dd", "in_trash": true}</example> Notes: Cannot delete/create title properties. Max one unique_id property. Cannot update synced databases. Use "fetch" first to see current schema and get the data source ID from <data-source url="collection://..."> tags.

Overview

Update a Notion page's properties or content.

Properties

Notion page properties are a JSON map of property names to SQLite values. For pages in a database:

• ALWAYS use the "fetch" tool first to get the data source schema and the exact property names.
• Provide a non-null value to update a property's value.
• Omitted properties are left unchanged.

IMPORTANT: Some property types require expanded formats:

• Date properties: Split into "date:{property}:start", "date:{property}:end" (optional), and "date:{property}:is_datetime" (0 or 1)
• Place properties: Split into "place:{property}:name", "place:{property}:address", "place:{property}:latitude", "place:{property}:longitude", and "place:{property}:google_place_id" (optional)
• Number properties: Use JavaScript numbers (not strings)
• Checkbox properties: Use "__YES__" for checked, "__NO__" for unchecked

Special property naming: Properties named "id" or "url" (case insensitive) must be prefixed with "userDefined:" (e.g., "userDefined:URL", "userDefined:id") For pages outside of a database:

• The only allowed property is "title", which is the title of the page in inline markdown format.

Content

Notion page content is a string in Notion-flavored Markdown format. IMPORTANT: For the complete Markdown specification, first fetch the MCP resource at notion://docs/enhanced-markdown-spec. Do NOT guess or hallucinate Markdown syntax. Use "insert_content" to add content at the beginning or end of a page. If position is omitted, the content is appended to the end of the page. Before using "update_content", use the "fetch" tool first to get the existing content and find the Markdown snippets to use in the "update_content" command's old_str fields.

Preserving Child Pages and Databases

When using "replace_content", the operation will check if any child pages or databases would be deleted. If so, it will fail with an error listing the affected items. To preserve child pages/databases, include them in new_str using <page url="..."> or <database url="..."> tags. Get the exact URLs from the "fetch" tool output. CRITICAL: To intentionally delete child content: if the call failed with validation and requires allow_deleting_content to be true, DO NOT automatically assume the content should be deleted. ALWAYS show the list of pages to be deleted and ask for user confirmation before proceeding.

Icon and Cover

You can set or remove a page's icon and cover alongside any command.

• "icon": An emoji character (e.g. "🚀"), a custom emoji by name (e.g. ":rocket_ship:"), or an external image URL. Use "none" to remove. Omit to leave unchanged.
• "cover": An external image URL. Use "none" to remove. Omit to leave unchanged.

Examples

<example description="Update page icon and cover"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_properties", "properties": {"title": "My Page"}, "icon": "🚀", "cover": "https://example.com/cover.jpg" } </example> <example description="Update page properties"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_properties", "properties": { "title": "New Page Title", "status": "In Progress", "priority": 5, "checkbox": "__YES__", "date:deadline:start": "2024-12-25", "date:deadline:is_datetime": 0, "place:office:name": "HQ", "place:office:latitude": 37.7749, "place:office:longitude": -122.4194 } } </example> <example description="Replace the entire content of a page"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "replace_content", "new_str": "

New Section

Updated content goes here" } </example> <example description="Update specific content in a page (search-and-replace)"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_content", "content_updates": [ { "old_str": "

Old Section

Old content here", "new_str": "

New Section

Updated content goes here" } ] } </example> <example description="Insert new content at the top of a page"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "insert_content", "content": "

Latest update

Status update goes here", "position": { "type": "start" } } </example> <example description="Insert content after a specific location"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_content", "content_updates": [ { "old_str": "

Previous section

Existing content", "new_str": "

Previous section

Existing content

New Section

Content to insert goes here" } ] } </example> <example description="Multiple content updates in a single call"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_content", "content_updates": [ { "old_str": "Old text 1", "new_str": "New text 1" }, { "old_str": "Old text 2", "new_str": "New text 2" } ] } </example>

Templates

You can apply a template to an existing page using the "apply_template" command. The template content is appended to the page asynchronously. Get template IDs from the <templates> section in the fetch tool results for a database, or use any page ID as a template. <example description="Apply a template to an existing page"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "apply_template", "template_id": "a5da15f6-b853-455d-8827-f906fb52db2b" } </example>

Verification

You can verify or unverify a page using the "update_verification" command. Verification marks a page as reviewed and up-to-date. Requires a Business or Enterprise plan (or the page must be in a wiki). <example description="Verify a page for 90 days"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_verification", "verification_status": "verified", "verification_expiry_days": 90 } </example> <example description="Verify a page indefinitely"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_verification", "verification_status": "verified" } </example> <example description="Remove verification from a page"> { "page_id": "f336d0bc-b841-465b-8045-024475c079dd", "command": "update_verification", "verification_status": "unverified" } </example>

Update a view's name, filters, sorts, or display configuration. Use "fetch" to get view IDs from database responses. Only include fields you want to change. The "configure" param uses the same DSL as create_view. Use CLEAR to remove settings:

• CLEAR FILTER — remove all filters
• CLEAR SORT — remove all sorts
• CLEAR GROUP BY — remove grouping

See notion://docs/view-dsl-spec resource for full syntax. <example description="Rename">{"view_id": "abc123", "name": "Sprint Board"}</example> <example description="Update filter">{"view_id": "abc123", "configure": "FILTER "Status" = "Done""}</example> <example description="Clear filter, add sort">{"view_id": "abc123", "configure": "CLEAR FILTER; SORT BY "Created" DESC"}</example> <example description="Update grouping">{"view_id": "abc123", "configure": "GROUP BY "Priority"; SHOW "Name", "Status""}</example>

Perform a search over:

• "internal": Semantic search over Notion workspace and connected sources (Slack, Google Drive, Github, Jira, Microsoft Teams, Sharepoint, OneDrive, Linear). Supports filtering by creation date and creator.
• "user": Search for users by name or email.

Auto-selects AI search (with connected sources) or workspace search (workspace-only, faster) based on user's access to Notion AI. Use content_search_mode to override. Use "fetch" tool for full page/database contents after getting search results. For Notion results, pass the result's "id" field to fetch tool's "id" param. Set page_size (default 10, max 25) and max_highlight_length (default 200, 0 to omit) as low as possible to minimize response size. To search within a database: First fetch the database to get the data source URL (collection://...) from <data-source url="..."> tags, then use that as data_source_url. For multi-source databases, match by view ID (?v=...) in URL or search all sources separately. Don't combine database URL/ID with collection:// prefix for data_source_url. Don't use database URL as page_url. <example description="Search with date range filter (only documents created in 2024)"> { "query": "quarterly revenue report", "query_type": "internal", "filters": { "created_date_range": { "start_date": "2024-01-01", "end_date": "2025-01-01" } } } </example> <example description="Teamspace + creator filter"> {"query": "project updates", "query_type": "internal", "teamspace_id": "f336d0bc-b841-465b-8045-024475c079dd", "filters": {"created_by_user_ids": ["a1b2c3d4-e5f6-7890-abcd-ef1234567890"]}} </example> <example description="Database with date + creator filters"> {"query": "design review", "data_source_url": "collection://f336d0bc-b841-465b-8045-024475c079dd", "filters": {"created_date_range": {"start_date": "2024-10-01"}, "created_by_user_ids": ["a1b2c3d4-e5f6-7890-abcd-ef1234567890", "b2c3d4e5-f6a7-8901-bcde-f12345678901"]}} </example> <example description="User search"> {"query": "john@example.com", "query_type": "user"} </example>