Managing Notion

Managing Notion

Tools for Notion workspace management including pages, databases (data sources), blocks, and comments.

Important: All tools require a parameter object. Pass {} for tools with no required parameters.

Tools (21 total)

Users

Search

Pages

Blocks

Data Sources (Databases)

Comments

Examples

Search and Retrieve

import { APIPostSearch, APIRetrieveAPage, APIGetBlockChildren } from '@connections/notion';

// Search (pass empty object if no query)
const results = await APIPostSearch({
  query: 'meeting notes',
  filter: { property: 'object', value: 'page' }
});

// Get page
const page = await APIRetrieveAPage({ page_id: 'page-id-here' });

// Get blocks
const blocks = await APIGetBlockChildren({ block_id: page.id });

Create Page

import { APIPostPage } from '@connections/notion';

const page = await APIPostPage({
  parent: { page_id: 'parent-page-id' },
  properties: {
    title: [{ text: { content: 'New Page' } }]
  },
  children: [
    {
      object: 'block',
      type: 'paragraph',
      paragraph: { rich_text: [{ text: { content: 'Hello' } }] }
    }
  ]
});

Query Database

import { APIQueryDataSource } from '@connections/notion';

const results = await APIQueryDataSource({
  data_source_id: 'database-id',
  filter: {
    property: 'Status',
    status: { equals: 'In Progress' }
  },
  sorts: [{ property: 'Due Date', direction: 'ascending' }]
});

Property Types

Block Types

paragraph, heading_1, heading_2, heading_3, bulleted_list_item, numbered_list_item, to_do, toggle, code, quote, callout, divider, table, image, video, file

Common Errors

Output Format

Present results as a structured report:

Managing Notion Report
══════════════════════
Resources discovered: [count]

Resource       Status    Key Metric    Issues
──────────────────────────────────────────────
[name]         [ok/warn] [value]       [findings]

Summary: [total] resources | [ok] healthy | [warn] warnings | [crit] critical
Action Items: [list of prioritized findings]

Target ≤50 lines of output. Use tables for multi-resource comparisons.

Anti-Hallucination Rules

1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
5. ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.

Counter-Rationalizations