Skip to main content
Glama

notion_retrieve_bot_user

Retrieve the bot user associated with the current Notion token to identify workspace permissions and access details.

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

  • The core handler function `retrieveBotUser` in NotionClientWrapper that makes the API call to /users/me to retrieve the bot user.
    async retrieveBotUser(): Promise<UserResponse> {
      const response = await fetch(`${this.baseUrl}/users/me`, {
        method: "GET",
        headers: this.headers,
      });
      return response.json();
    }
  • The Tool schema definition for 'notion_retrieve_bot_user', including input schema with dummy param.
    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"],
      },
    };
  • Registration in the tool dispatch switch case: calls notionClient.retrieveBotUser()
    case "notion_retrieve_bot_user": {
      response = await notionClient.retrieveBotUser();
      break;
    }
  • Registration in the listTools handler: includes retrieveBotUserTool in the allTools array.
    schemas.retrieveBotUserTool,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a retrieval operation, implying it's likely read-only, but doesn't confirm this or describe other behaviors like authentication requirements, rate limits, error conditions, or what the response contains. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 appropriately sized and front-loaded, making it easy for an agent to parse quickly. Every word earns its place.

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 a Notion API tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the bot user data includes, how it differs from regular users, or any authentication context. For a tool that likely returns structured user data, more context about the response would be helpful, especially without an output schema.

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 schema description coverage is 100%, so the schema already fully documents both parameters. The description adds no additional meaning about parameters beyond what's in the schema. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter info in the description, which applies here.

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. However, it doesn't explicitly differentiate from sibling tools like 'notion_retrieve_user' or 'notion_list_all_users', which could cause confusion about when to use this specific bot user retrieval versus general user 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. There's no mention of prerequisites (e.g., needing a valid token), comparison to sibling tools like 'notion_retrieve_user', or specific use cases for retrieving bot users versus regular users. This leaves the agent without contextual direction.

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