Skip to main content
Glama

notion_retrieve_block

Retrieve content from Notion blocks in JSON or Markdown format for reading, writing, or modifying workspace data.

Instructions

Retrieve a block from Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesThe ID of the block to retrieve.It should be a 32-character string (excluding hyphens) formatted as 8-4-4-4-12 with hyphens (-).
formatNoSpecify 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

  • Core implementation of the notion_retrieve_block tool: fetches the Notion block by ID using the API.
    async retrieveBlock(block_id: string): Promise<BlockResponse> {
      const response = await fetch(`${this.baseUrl}/blocks/${block_id}`, {
        method: "GET",
        headers: this.headers,
      });
    
      return response.json();
    }
  • Server-side handler for notion_retrieve_block: validates arguments and delegates to NotionClientWrapper.retrieveBlock.
    case "notion_retrieve_block": {
      const args = request.params
        .arguments as unknown as args.RetrieveBlockArgs;
      if (!args.block_id) {
        throw new Error("Missing required argument: block_id");
      }
      response = await notionClient.retrieveBlock(args.block_id);
      break;
    }
  • Tool schema definition including name, description, and input schema for notion_retrieve_block.
    export const retrieveBlockTool: Tool = {
      name: "notion_retrieve_block",
      description: "Retrieve a block from Notion",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "The ID of the block to retrieve." + commonIdDescription,
          },
          format: formatParameter,
        },
        required: ["block_id"],
      },
    };
  • Registers the notion_retrieve_block tool (via schemas.retrieveBlockTool) in the MCP server's listTools handler.
    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),
      };
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves a block but doesn't mention any behavioral traits such as rate limits, authentication requirements, error conditions, or what the output looks like (e.g., structure, size limits). For a retrieval tool with no annotation coverage, this leaves significant gaps in understanding how it behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—a single sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to scan. Every word earns its place, though this conciseness comes at the cost of detail in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of retrieving a Notion block, the lack of annotations, and no output schema, the description is incomplete. It doesn't explain what a block is, what data it returns, or how it fits into the broader Notion API context. For a tool with 2 parameters and no structured output information, more context is needed to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents both parameters ('block_id' and 'format'). The description adds no additional meaning beyond what's in the schema. According to the rules, with high schema coverage, the baseline score is 3, as the description doesn't need to compensate but also doesn't enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Retrieve') and resource ('a block from Notion'), which is clear but basic. It doesn't distinguish this tool from sibling tools like 'notion_retrieve_page' or 'notion_retrieve_database', which also retrieve Notion resources. The purpose is understandable but lacks specificity about what makes a 'block' different from other retrievable entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't explain when to retrieve a block versus a page or database, or how it relates to siblings like 'notion_retrieve_block_children'. The input schema includes some usage hints for the 'format' parameter, but the tool description itself offers no contextual guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/suekou/mcp-notion-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server