Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NOTION_TOKENYesYour Notion integration token. Get it from https://www.notion.so/my-integrations → Create integration → Copy token → Share pages with integration

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pagesA

Page CRUD for individual pages and database rows.

Actions (required params -> optional):

  • create (parent_id -> title, content, properties, icon, cover)

  • get (page_id -> content_limit, content_cursor): returns markdown content; bounded reads return content_truncated and next_cursor

  • get_property (page_id, property_id)

  • update (page_id -> title, content, append_content, properties, icon, cover, archived)

  • move (page_id, parent_id)

  • archive (page_id) / restore (page_id)

  • duplicate (page_id -> parent_id)

Use databases instead for querying or bulk row operations. Property format: simple values auto-convert -- string for title/rich_text/select/status, number for number, boolean for checkbox, string[] for multi_select, ISO date "2025-01-15" for date. Example: properties: {"Name": "My Page", "Status": "In Progress", "Tags": ["urgent", "work"]}

databasesA

Database schema, query, and bulk row operations.

Actions (required params -> optional):

  • create (parent_id -> title, properties, is_inline, icon, cover)

  • get (database_id)

  • query (database_id -> filters, sorts, limit, search)

  • create_page (database_id, pages[{properties}])

  • update_page (database_id, page_id, page_properties)

  • delete_page (database_id, page_ids)

  • create_data_source / update_data_source / update_database / list_templates

Use pages instead for single page CRUD. Accepts both database_id (from URL) and data_source_id (from workspace search) -- auto-resolved.

blocksA

Read and modify block-level content within pages.

Actions (required params -> optional):

  • get (block_id): retrieve single block

  • children (block_id): list child blocks

  • append (block_id, content -> position, after_block_id): add markdown content at position

  • update (block_id, content): replace text block content

  • delete (block_id): remove block

Use pages for page metadata/properties. Page IDs are valid block IDs. update only works on text blocks (paragraph, headings, lists, quote, to_do, code). Image/file blocks contain signed URLs (1h expiry). append supports position: "start" (prepend), "end" (default), "after_block" (requires after_block_id).

usersA

Get user information.

Actions (required params):

  • list: all workspace users (requires admin permissions)

  • get (user_id): single user info

  • me: current bot/integration user

  • from_workspace: extract users from accessible pages (use if list fails)

workspaceA

Search workspace and get workspace info.

Actions (required params -> optional):

  • info: workspace name, plan, and bot user

  • search (-> query, filter.object="page"|"data_source", sort, limit): find pages/databases shared with integration

commentsA

Manage page comments.

Actions (required params -> optional):

  • list (page_id): all comments on a page

  • get (comment_id): single comment

  • create (content -> page_id for new discussion, discussion_id for reply)

content_convertA

Convert between markdown and Notion block JSON. Directions: markdown-to-blocks (input: markdown string), blocks-to-markdown (input: JSON array of Notion blocks or JSON string). Most tools (pages, blocks) handle markdown automatically -- use this only for preview/validation. Supported markdown: headings, lists, to-do, code blocks, blockquotes, dividers, callouts (> [!NOTE]), toggles (), tables, images, bookmarks, embeds, equations ($$), columns (:::columns), [toc], [breadcrumb]. Inline: bold, italic, code, strike, link.

file_uploadsA

Upload files to Notion.

Actions (required params -> optional):

  • create (filename -> content_type, mode="single"|"multi_part", number_of_parts)

  • send (file_upload_id, file_content -> part_number): base64-encoded content

  • complete (file_upload_id)

  • retrieve (file_upload_id)

  • list (-> limit)

Max 20MB direct, multi-part for larger files.

helpA

Get full documentation for a tool. Use when compressed descriptions are insufficient.

configA

Manage server configuration and credential state.

Actions:

  • status: current credential state and token source

  • setup_status: credential/setup state only (alias-equivalent to status for notion; kept for cross-server parity)

  • setup_start (-> force): show how to store a Notion token with notion auth

  • setup_reset: clear stored credentials, return to awaiting_setup

  • setup_complete: re-check credentials after external config changes

  • set: update a runtime setting (notion has no mutable settings; returns info)

  • cache_clear: clear any cached state (no-op for notion)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Pages Tool Docs
Databases Tool Docs
Blocks Tool Docs
Users Tool Docs
Workspace Tool Docs
Comments Tool Docs
Content Convert Tool Docs
File Uploads Tool Docs

TDQS

A4.1/5.0

Scored across 10 tools

Disambiguation4/5

Tools are largely separated by Notion resource (pages, blocks, databases, comments, users, workspace), so most selections are clear. There is some overlap between pages.update/append_content and blocks.append, and between databases row operations and pages CRUD, though the descriptions provide guidance.

Naming Consistency4/5

The dominant pattern is resource-noun tools with action subcommands, which is predictable and readable. Minor deviations include singular config/workspace, plural file_uploads/users/pages, and utility names like help and content_convert.

Tool Count5/5

At 10 tools, the server is well-scoped for the Notion API surface. Each tool groups a meaningful resource area without forcing an excessive number of separate tools.

Completeness4/5

The surface covers the main Notion workflows: pages, blocks, databases, comments, users, workspace search, file uploads, and content conversion. Minor gaps or unclear areas remain around database-level archive/delete and block reordering/moving.

Maintenance

ActivityActive
ResponsivenessWithin a week