Skip to main content
Glama

get-block

Retrieve specific Notion blocks by ID to access content, structure, or properties within your workspace.

Instructions

Retrieve a block by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
block_idYesID of the block to retrieve

Implementation Reference

  • The handler logic for the 'get-block' tool. It extracts the block_id from arguments, removes any dashes from the ID, retrieves the block using the Notion SDK's notion.blocks.retrieve method, and returns the response as a JSON string 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:268-281 (registration)
    Registration of the 'get-block' tool in the response to the tools/list MCP method, providing the tool's name, description, and input schema.
    {
      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 definition for the 'get-block' tool, specifying that a string 'block_id' is required.
    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 the full burden of behavioral disclosure. It states the action ('Retrieve') but doesn't describe what happens on failure (e.g., if the block ID is invalid), whether it requires authentication, rate limits, or the format of the returned data. For a read operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place without redundancy or unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete for a retrieval tool. It doesn't explain what a 'block' is in this context, what data is returned, or error handling. With no structured fields to rely on, the description should provide more context about the tool's operation and results, but it falls short.

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, with the single parameter 'block_id' clearly documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain block ID format or examples). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 unambiguous. However, it doesn't differentiate this tool from similar siblings like 'get-block-children' or 'get-page', which also retrieve content by ID. The description is specific but lacks sibling distinction.

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' (for child blocks), 'get-page' (for pages), and 'search' (for broader queries), there's no indication of when this specific retrieval by block ID is appropriate. No exclusions or prerequisites are mentioned.

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/Sjotie/notionMCP'

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