Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

notion-mcp__notion_search

Read-only

Searches the Notion pages and data sources shared with the DataToRAG connection, by title. Notion's search matches titles, not page content, and Notion describes its index as not immediate and not guaranteed complete, so a page created moments ago can be missing. Takes an optional query, an optional object type, a page size and a cursor. Each result is reduced to id, object (page or data_source), title, url, parent ({type, id}) and last_edited_time. The result is {results, has_more, next_cursor}, with the same shape when there are no results. has_more true means more results exist than this page holds, and next_cursor is the cursor argument that returns them. A page or database that exists but is not shared with the connection does not appear.

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": "notion-mcp__notion_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoText matched against titles. Absent or empty returns every shared page and data source, most recently edited at the top.
cursorNoThe next_cursor value from an earlier call with the same arguments. Returns the page of results after that one. Absent for the start of the list.
objectNoLimits results to pages or to data sources (the tables inside a database). Absent returns both.
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
page_sizeNoHow many results one call returns, from 1 to 100. Default 20. A full page comes back with has_more true and a next_cursor for the rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safety profile, and the description stays consistent with it while adding real context: index staleness, sharing-based visibility limits, per-result field reduction, and pagination semantics. That is solid added value, though it does not discuss rate limits or ordering beyond the schema's 'most recently edited' note.

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 purpose, then constraints, then arguments, then return shape. Dense but each sentence carries information, with only the parameter-summary sentence being largely redundant against the schema.

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

Completeness5/5

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

With no output schema, the description takes on the return contract itself and does so fully: result fields, the {results, has_more, next_cursor} envelope, the empty-result case, and how has_more maps to next_cursor. Combined with the sharing caveat, an agent has everything needed to call and paginate correctly.

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%, so the schema already defines every parameter including the account override, which the description omits. The description only adds the linkage that next_cursor is the cursor argument for the next call; otherwise it restates the parameter list rather than enriching it.

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: searches Notion pages and data sources shared with the connection, matched by title. It also scopes the tool by title-only matching, which separates it from content-based retrieval and from notion_query_data_source's row retrieval.

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?

Gives useful decision context: title-only matching, an index that is 'not immediate and not guaranteed complete', and the fact that unshared pages never appear. It stops short of naming an explicit alternative (e.g. notion_get_page by id for a just-created page), so the fallback path must be inferred.

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

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