Skip to main content
Glama

notion_retrieve_block

Retrieve content from Notion blocks in JSON or Markdown format to read, modify, or integrate with other tools.

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 handler function that executes the Notion API GET request to retrieve a specific block by ID.
    async retrieveBlock(block_id: string): Promise<BlockResponse> {
      const response = await fetch(`${this.baseUrl}/blocks/${block_id}`, {
        method: "GET",
        headers: this.headers,
      });
    
      return response.json();
    }
  • Tool schema definition including input schema, name, and description 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"],
      },
    };
  • Server dispatch case that handles the tool call by invoking the client retrieveBlock method.
    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;
    }
  • Registration of the tool schema in the listTools response.
    schemas.retrieveBlockTool,
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 action ('retrieve') but does not describe traits like authentication requirements, rate limits, error handling, or what the return value looks like (e.g., structure, pagination). For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool 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 a single, clear sentence with no wasted words. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration. Every part of the sentence earns its place by conveying the essential action.

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 block (with parameters like format options) and no output schema or annotations, the description is incomplete. It lacks details on return values, error cases, or behavioral context, which are crucial for effective tool use. The description does not compensate for the absence of structured data, leaving gaps in understanding.

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?

The input schema has 100% description coverage, detailing both parameters ('block_id' and 'format') with enums and defaults. The description does not add any meaning beyond what the schema provides, such as explaining parameter interactions or use cases. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the heavy lifting without extra value from the description.

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 verb ('retrieve') and resource ('a block from Notion'), which clarifies the basic action. However, it does not differentiate this tool from sibling tools like 'notion_retrieve_page' or 'notion_retrieve_database', leaving ambiguity about what specific type of content is being retrieved. It is vague in distinguishing the scope from other retrieval tools.

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. It does not mention sibling tools like 'notion_retrieve_page' or 'notion_retrieve_database', nor does it explain prerequisites such as needing a valid block ID. Usage is implied only through the tool name and parameters, with no explicit context or exclusions provided.

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/kimjungyeol/mcp-notion-server'

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