Skip to main content
Glama

smithery-notion

by ai.smithery
OverviewDiscussionsAdmin

search

Search pages and databases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by last edited or created time
queryYesSearch query
filterNoFilter by object type (page or database)
page_sizeNoNumber of results per page
start_cursorNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / filter / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / filter / description
      Previous value: -"Filter by object type"New value: +"Filter by object type (page or database)"
    • removedInput schema / properties / filter / properties
      Removed value: -{
-  "property": {
-    "const": "object",
-    "type": "string"
-  },
-  "value": {
-    "enum": [
-      "page",
-      "database"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / filter / required
      Removed value: -[
-  "value",
-  "property"
-]
    • removedInput schema / properties / page_size / default
      Removed value: -10
    • removedInput schema / properties / page_size / maximum
      Removed value: -100
    • removedInput schema / properties / page_size / minimum
      Removed value: -1
    • changedInput schema / properties / sort / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort results"New value: +"Sort by last edited or created time"
    • removedInput schema / properties / sort / properties
      Removed value: -{
-  "direction": {
-    "enum": [
-      "ascending",
-      "descending"
-    ],
-    "type": "string"
-  },
-  "timestamp": {
-    "enum": [
-      "last_edited_time"
-    ],
-    "type": "string"
-  }
-}
    • removedInput schema / properties / sort / required
      Removed value: -[
-  "direction",
-  "timestamp"
-]
    • addedInput schema / required
      Added value: +[
+  "query"
+]
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but discloses nothing about behavioral traits: pagination behavior, rate limits, whether results are sorted by relevance, or if the operation is read-only (implied but not stated).

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?

Extremely concise at three words with no redundancy. However, given the tool complexity (5 params, nested objects, pagination), it is insufficiently descriptive rather than appropriately lean.

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

Completeness2/5

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

For a search tool with nested filter/sort objects (additionalProperties: {}), no output schema, and no annotations, the description is incomplete. It fails to explain valid filter values, sorting options, or return structure.

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 all five parameters documented (query, filter, sort, page_size, start_cursor). The description adds no parameter-specific guidance, meeting the baseline for well-documented schemas.

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

Purpose3/5

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

The description states the verb (search) and target resources (pages and databases), distinguishing it from siblings like get_page or list_databases. However, it fails to specify the search semantics (e.g., full-text vs title-only, case sensitivity), keeping it at minimum viable clarity.

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

Usage Guidelines2/5

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

No guidance provided on when to use this versus query_database (which searches within a specific database) or list_databases (which lists all). The agent cannot determine if search is the right tool for filtering by object type versus using the filter parameter.

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

All smithery-notion toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources