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,

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'Retrieve', implying no side effects, but does not mention authentication needs, error cases (e.g., invalid block_id), rate limits, or whether the operation is safe. Essential behavioral context is missing.

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?

Single sentence, no fluff, front-loaded with the core purpose. Every word earns its place. Cannot be more concise while remaining complete.

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?

Despite the tool's simplicity, the description lacks information about return values or behavior. There is no output schema, so the description should at least hint at what the response contains (e.g., block content, metadata). It does not, making it incomplete for an agent that needs to use the result.

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

Parameters4/5

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

Schema coverage is 100%, and the description adds meaningful value beyond the schema. The 'format' parameter includes a clear decision tree for when to use 'markdown' vs 'json', which helps the agent choose appropriately. The 'block_id' description specifies the expected format. This is above baseline.

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

Purpose4/5

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

The description clearly states the verb 'Retrieve' and the resource 'a block', which is specific enough to understand the tool's basic function. However, it does not differentiate from closely related siblings like 'notion_retrieve_block_children' or 'notion_retrieve_page', so the agent would need to infer distinctions from context.

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?

No guidance is provided on when to use this tool versus alternatives such as 'notion_retrieve_block_children' or 'notion_retrieve_page'. There are no exclusions, prerequisites, or context hints, leaving the agent to guess based on tool names alone.

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