notion_update_block
Modify content in Notion blocks by replacing field values based on block type, supporting JSON or Markdown response formats.
Instructions
Update the content of a block in Notion based on its type. The update replaces the entire value for a given field.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| block | Yes | The updated content for the block. Must match the block's type schema. | |
| block_id | Yes | The ID of the block to update.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-). | |
| format | No | Specify the response format. 'json' returns the original data structure, 'markdown' returns a more readable format. Use 'markdown' when the user only needs to read the page and isn't planning to write or modify it. Use 'json' when the user needs to read the page with the intention of writing to or modifying it. | markdown |
Implementation Reference
- src/client/index.ts:89-100 (handler)Core handler function in NotionClientWrapper that performs the PATCH request to Notion API /blocks/{block_id} to update the block content.async updateBlock( block_id: string, block: Partial<BlockResponse> ): Promise<BlockResponse> { const response = await fetch(`${this.baseUrl}/blocks/${block_id}`, { method: "PATCH", headers: this.headers, body: JSON.stringify(block), }); return response.json(); }
- src/types/schemas.ts:99-119 (schema)Tool schema definition for notion_update_block, specifying input parameters and description.export const updateBlockTool: Tool = { name: "notion_update_block", description: "Update the content of a block in Notion based on its type. The update replaces the entire value for a given field.", inputSchema: { type: "object", properties: { block_id: { type: "string", description: "The ID of the block to update." + commonIdDescription, }, block: { type: "object", description: "The updated content for the block. Must match the block's type schema.", }, format: formatParameter, }, required: ["block_id", "block"], }, };
- src/server/index.ts:100-110 (registration)Registration and dispatch in the MCP server's CallToolRequest handler switch statement, which validates args and calls the client updateBlock method.case "notion_update_block": { const args = request.params .arguments as unknown as args.UpdateBlockArgs; if (!args.block_id || !args.block) { throw new Error("Missing required arguments: block_id and block"); } response = await notionClient.updateBlock( args.block_id, args.block ); break;
- src/types/args.ts:32-36 (schema)TypeScript interface for the arguments used in the server handler for notion_update_block.export interface UpdateBlockArgs { block_id: string; block: Partial<BlockResponse>; format?: "json" | "markdown"; }
- src/server/index.ts:302-325 (registration)Registration of the tool in the ListToolsRequest handler by including updateBlockTool in the list of available tools.server.setRequestHandler(ListToolsRequestSchema, async () => { const allTools = [ schemas.appendBlockChildrenTool, schemas.retrieveBlockTool, schemas.retrieveBlockChildrenTool, schemas.deleteBlockTool, schemas.updateBlockTool, schemas.retrievePageTool, schemas.updatePagePropertiesTool, schemas.listAllUsersTool, schemas.retrieveUserTool, schemas.retrieveBotUserTool, schemas.createDatabaseTool, schemas.queryDatabaseTool, schemas.retrieveDatabaseTool, schemas.updateDatabaseTool, schemas.createDatabaseItemTool, schemas.createCommentTool, schemas.retrieveCommentsTool, schemas.searchTool, ]; return { tools: filterTools(allTools, enabledToolsSet), };