Notion MCP by InsightfulPipe

Notion Setup Helper

query_contexts

Read-only

Helper for planning InsightfulPipe Notion requests.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, gcp_project_id, other source metadata, AND available_actions (all read-only actions you can call).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

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": {
      "request": "<request>"
    },
    "name": "query_contexts"
  }
}

Input Schema

Name	Required	Description	Default
`actions`	No
`request`	Yes
`brand_id`	No
`platform`	No
`workspace_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

readOnlyHint=true already declares the safety profile, and the description is consistent with it (all modes are retrieval). It adds value beyond annotations by disclosing what each call returns — workspace_id, brand_id, gcp_project_id, available_actions, and per-action request bodies/identifiers/notes. No rate limits, auth requirements, or error behavior are mentioned.

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 purpose sentence followed by a numbered step layout that mirrors the correct invocation order, with each line carrying distinct information. Slightly repetitive parenthetical annotations, but no sentence is 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?

For a multi-mode dispatcher with an output schema present, the description covers the workflow the agent must follow and even summarizes return contents per mode. The unexplained 'platform' parameter and the absence of any pointer to the sibling executor are the only material omissions.

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 0%, so the description must carry the full burden. It explains four of five parameters well (request modes 'accounts'/'brands'/'available_actions'/'actions_details', the actions array sourced from available_actions, and that brands requires brand_id + workspace_id), but the 'platform' parameter is never mentioned anywhere in the description or schema, leaving a real gap.

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 states this is a discovery/setup helper that returns workspace metadata and action specifications for InsightfulPipe Notion requests, with a concrete verb-and-resource breakdown across four request modes. It does not name or differentiate itself from the sibling tools (execute_action, query_data), so an agent must infer that this is the prerequisite step rather than the executor.

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

Usage Guidelines4/5

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

Unusually explicit sequencing: Step 1 'accounts', Step 2 'actions_details' marked 'REQUIRED before querying', plus two clearly labeled optional calls. It even steers away from a redundant call by noting available_actions is 'already included in accounts response'. It stops short of explicitly saying 'use execute_action for the actual request', so the routing to siblings is implied rather than stated.

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 tools Inspect

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.