Skip to main content
Glama

mcp-notion__notion-get-sidebar-tabs

Read-onlyIdempotent

Get the current user's Notion sidebar tabs, in order, plus catalogs of the shortcuts and sections they can add. Shortcut groups are not returned or editable. Catalog examples are valid update_sidebar_tabs inputs, including configured New page shortcuts and database view sections. Each tab is independent: built-in items may appear in more than one tab. Call this before update_sidebar_tabs. Through Royally: its server marks it read-only, so it runs straight away.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcp-notion__notion-get-sidebar-tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillNoFor tracking only: the name of the agent skill you are following for this task, such as notion-meeting-prep. Omit if you are not following a skill.
site_idNoSite to run this tool on: ded71e55-0da4-4a52-8f14-1224fa9979b9 (https://mcp.notion.com/mcp)
instructions_versionNoNotion setup instructions version, such as 0.0.2. Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: tabs are independent, built-in items may appear in multiple tabs, and the return contains both tabs and addable catalogs. The closing line about the server marking it read-only and running 'straight away' largely restates readOnlyHint/destructiveHint=false, but usefully signals no confirmation step.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and well ordered (what it returns, then constraints, then sequencing). Dense but each sentence carries information; only the 'Through Royally... runs straight away' sentence is somewhat redundant against the annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry the return shape, and it does describe tabs in order plus shortcut/section catalogs. Minor gap: it does not say how tabs are identified or what fields each tab carries, which an agent may need before constructing update_sidebar_tabs calls.

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 coverage is 100% and all three parameters (skill, site_id, instructions_version) are self-documented with descriptions, so the schema does the heavy lifting. The description adds no parameter-level meaning, which is the expected baseline here.

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

Purpose5/5

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

States a specific verb and resource ('Get the current user's Notion sidebar tabs') plus scope ('in order, plus catalogs of the shortcuts and sections they can add'). No sibling tool touches sidebar tabs, and the definition makes that distinct role obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing guidance: 'Call this before update_sidebar_tabs,' with the note that catalog examples are valid update_sidebar_tabs inputs. It also states an exclusion — shortcut groups are neither returned nor editable — so the agent knows the boundary of what it can act on.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources