Skip to main content
Glama

Notion_connect

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Notion Search

notion_search
Read-onlyIdempotent

Search your Notion workspace by keyword. Returns matching page/database titles, IDs, and types to locate content quickly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query text
filterNoFilter by object type: "page" or "database" (optional)
page_sizeNoNumber of results to return (default 10, max 100)
start_cursorNoPagination cursor for next page of results

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectNoAlways 'list'
resultsNoArray of matching pages and databases
has_moreNoWhether more results exist
next_cursorNoPagination cursor for next page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "has_more": {
+      "description": "Whether more results exist",
+      "type": "boolean"
+    },
+    "next_cursor": {
+      "description": "Pagination cursor for next page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "object": {
+      "description": "Always 'list'",
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of matching pages and databases",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Notion object ID",
+            "type": "string"
+          },
+          "object": {
+            "description": "Type of result",
+            "enum": [
+              "page",
+              "database"
+            ],
+            "type": "string"
+          },
+          "title": {
+            "description": "Title content blocks",
+            "items": {
+              "properties": {
+                "text": {
+                  "properties": {
+                    "content": {
+                      "description": "Title text",
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": {
+                  "description": "Block type",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "project timeline"
+  },
+  {
+    "filter": "page",
+    "page_size": 20,
+    "query": "meeting notes"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that it returns titles, IDs, and types, which is consistent and provides extra context about the output format.

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 sentence that is concise and front-loaded with the key purpose. No extraneous information.

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?

Given the tool has an output schema and annotations covering safety, the description is largely complete. It does not explicitly mention pagination (start_cursor) but that is detailed in the schema. A small gap exists, but overall it is adequate.

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%, with each parameter described in the schema. The description reiterates 'keyword' corresponding to 'query' but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states 'Search your Notion workspace by keyword' and specifies the returned data (titles, IDs, types). It distinguishes itself from sibling tools like notion_get_database (specific database) and notion_get_page (specific page) by emphasizing workspace-wide search.

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

Usage Guidelines3/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives such as notion_query_database or notion_list_pages. Usage context is implied but not clarified.

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

All Notion_connect 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