Skip to main content
Glama

get-block

Retrieve specific Notion content blocks using their unique ID with the 'get-block' tool, integrating directly into the Notion MCP Server for AI-driven workspace management and content organization.

Instructions

Retrieve a block by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesID of the block to retrieve

Implementation Reference

  • The main handler for the 'get-block' tool. It extracts the block_id from arguments, removes any dashes from the ID, retrieves the block using the Notion API (notion.blocks.retrieve), and returns the JSON-stringified response wrapped in a text content block.
    else if (name === "get-block") {
      let { block_id } = args;
      
      // Remove dashes if present in block_id
      block_id = block_id.replace(/-/g, "");
    
      const response = await notion.blocks.retrieve({ block_id });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • server.js:266-279 (registration)
    Registration of the 'get-block' tool in the tools/list response, including its name, description, and input schema requiring a 'block_id' string.
    {
      name: "get-block",
      description: "Retrieve a block by its ID",
      inputSchema: {
        type: "object",
        properties: {
          block_id: {
            type: "string",
            description: "ID of the block to retrieve"
          }
        },
        required: ["block_id"]
      }
    },
  • Input schema for the 'get-block' tool, defining the required 'block_id' parameter.
    inputSchema: {
      type: "object",
      properties: {
        block_id: {
          type: "string",
          description: "ID of the block to retrieve"
        }
      },
      required: ["block_id"]
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'retrieve' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what happens with invalid IDs. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 perfectly concise at just four words. It's front-loaded with the essential action and resource, with zero wasted words. Every element of the description earns its place by communicating the core function efficiently.

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?

For a retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'block' represents in this context, what format the retrieved data will be in, or any limitations of the retrieval. Given the complexity implied by sibling tools (databases, pages, blocks), more context is needed.

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%, with the single parameter 'block_id' clearly documented in the schema. The description doesn't add any meaningful parameter information beyond what the schema already provides, so it meets the baseline for high schema coverage without adding extra value.

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 resource ('a block'), making the purpose understandable. It distinguishes this as a read operation rather than a creation or update tool. However, it doesn't explicitly differentiate from similar siblings like 'get-block-children' or 'get-page', which also retrieve content by ID.

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. With siblings like 'get-block-children' (retrieves child blocks), 'get-page' (retrieves pages), and 'search' (finds content), there's no indication of when this specific block retrieval is appropriate versus other lookup methods.

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

Related 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/emmanuelsystems/mcpnotionslack'

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