Skip to main content
Glama

notion_retrieve_bot_user

Retrieve the bot user associated with the current Notion API token to verify authentication and access permissions for workspace interactions.

Instructions

Retrieve the bot user associated with the current token in Notion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYesDummy parameter for no-parameter tools
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

  • Handles the MCP CallToolRequest for 'notion_retrieve_bot_user' by invoking the NotionClientWrapper's retrieveBotUser method.
    case "notion_retrieve_bot_user": {
      response = await notionClient.retrieveBotUser();
      break;
    }
  • Defines the input schema, name, and description for the 'notion_retrieve_bot_user' tool.
    export const retrieveBotUserTool: Tool = {
      name: "notion_retrieve_bot_user",
      description:
        "Retrieve the bot user associated with the current token in Notion",
      inputSchema: {
        type: "object",
        properties: {
          random_string: {
            type: "string",
            description: "Dummy parameter for no-parameter tools",
          },
          format: formatParameter,
        },
        required: ["random_string"],
      },
    };
  • Includes the tool schema in the list of available tools for the ListToolsRequest handler.
    schemas.retrieveBotUserTool,
  • Core implementation that fetches the bot user information from the Notion API endpoint '/users/me'.
    async retrieveBotUser(): Promise<UserResponse> {
      const response = await fetch(`${this.baseUrl}/users/me`, {
        method: "GET",
        headers: this.headers,
      });
      return response.json();
    }
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 'retrieve', implying a read operation, but doesn't mention authentication needs, rate limits, error handling, or what the response includes. For a tool with no annotations, 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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized, making it easy to parse quickly.

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 no annotations, no output schema, and a tool that retrieves user data, the description is incomplete. It doesn't explain what the bot user data includes, how it's formatted, or any constraints, leaving the agent with insufficient context for effective use.

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. The description adds no parameter-specific information beyond what's in the schema, such as clarifying 'random_string' or 'format' usage. Baseline 3 is appropriate as the schema handles the heavy lifting.

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 'bot user associated with the current token in Notion', making the purpose specific and understandable. It distinguishes from sibling tools like 'notion_retrieve_user' by specifying 'bot user' and 'associated with the current token', though it doesn't explicitly contrast with all siblings.

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, such as 'notion_retrieve_user' or other retrieval tools in the sibling list. It lacks context about prerequisites, scenarios, or exclusions, leaving usage unclear beyond the basic purpose.

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