Skip to main content
Glama
Sign In

Notion MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Notion Data

query_data
Read-only

Query Notion data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, gcp_project_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Notion is read-only here (OAuth scope notion.readonly): only SELECT queries succeed; DDL/DML/scripts are rejected by Google.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes meaningfully beyond the readOnlyHint/openWorldHint annotations by naming the OAuth scope (notion.readonly) and stating that DDL/DML/scripts are rejected, which tells an agent exactly what failure mode to avoid. It does not cover rate limits, pagination, or result-size behavior, and the stray 'rejected by Google' phrasing leaves the execution backend ambiguous. No contradiction with readOnlyHint=true.

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 step position and the REQUIRED/IMPORTANT blocks are scannable rather than padded. Slightly verbose in restating the two-step discovery twice (once in the numbered list, once in the IMPORTANT line), but no sentence is genuinely wasted.

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?

Output schema exists so return values need no explanation, annotations cover safety, and the discovery path for the opaque `body` parameter is spelled out. The main residual gap is that the description never characterizes the query result set (what 'SELECT queries' here actually return) or notes whether the body must be re-derived per action id.

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 single `body` parameter is an untyped free-form object at 0% schema coverage, and the description never enumerates its keys or shape inline. It does provide a genuine mitigation by routing the agent to query_contexts request='actions_details' to obtain the exact body structure, which is more than the schema offers, but the agent still cannot construct `body` from the description alone.

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?

Names a specific verb and resource (query Notion data) and positions itself as the terminal step of a three-step workflow, distinguishing it from query_contexts which supplies context rather than data. What a 'query' returns (rows? actions? arbitrary Notion objects?) is only inferrable from the read-only/SELECT framing, so it falls short of a fully crisp definition.

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?

Explicitly prescribes the prerequisite calls in order (query_contexts with request='accounts', then request='actions_details' with concrete action ids) and states the trigger condition for each. The 'IMPORTANT: Always call step 2' sentence removes any ambiguity about whether the discovery step is optional.

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

All Notion MCP by InsightfulPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources