Skip to main content
Glama
katekruger

notion-plus-mcp-server

by katekruger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Build Report Page

notion_build_report

Builds a Notion report page for a database in one call, combining summary stats, KPIs, charts, key tables, and optional Gantt timelines. Applies one filter across all sections.

Instructions

Build a report page for a database in one call: a summary callout (row count, completion, overdue), KPI numbers side by side, charts (live Notion chart views where Notion supports the type, rendered images otherwise), a table of key rows (e.g. overdue items), and a Mermaid Gantt chart of dated work. Every section is optional; where scopes the whole report. Image charts can be refreshed later with notion_create_chart. notion_undo trashes the page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kpisNoDefault: total rows plus a count per status group.
ganttNo
tableNo
titleNo
whereNoLimits every section to these rows.
chartsNo
parentYesPage to create the report under.
summaryNo
databaseYes
data_source_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / charts / items / properties / type / enum
      Previous value: -[
-  "bar",
-  "column",
-  "stacked_bar",
-  "stacked_column",
-  "grouped_column",
-  "line",
-  "area",
-  "stacked_area",
-  "pie",
-  "donut",
-  "scatter"
-]New value: +[
+  "bar",
+  "column",
+  "stacked_bar",
+  "stacked_column",
+  "grouped_column",
+  "line",
+  "area",
+  "stacked_area",
+  "pie",
+  "donut",
+  "scatter",
+  "histogram",
+  "heatmap",
+  "boxplot",
+  "waterfall",
+  "funnel",
+  "bullet",
+  "small_multiples",
+  "dual_axis",
+  "treemap",
+  "sankey",
+  "network"
+]
  2. First observedv0.10.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive write, and the description adds value beyond them: it discloses that charts may be live views or rendered images, that image charts are refreshable via notion_create_chart, and that notion_undo trashes the created page (i.e. it is reversible). It still omits permission requirements and what exactly is returned.

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 verb and outcome, then the optionality/scope rule, then related-tool notes. Three dense sentences that each carry information, though the section enumeration is somewhat packed.

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 10-parameter nested tool with no output schema, the description adequately conveys what is produced and the optionality/scope behavior. The main gap is that it does not describe the return value (e.g. the created page id/url), which has no schema to fall back on.

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 only 30%, so the description must compensate more than it does. It clarifies the role of `where` (scopes the whole report) and maps sections (summary, kpis, charts, table, gantt) to params, but leaves database, parent, title, and data_source_name unexplained.

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 (build) plus resource (a report page for a database) and explicitly notes it happens 'in one call'. It enumerates exactly what the page contains (summary callout, KPIs, charts, table, Gantt), distinguishing it from lower-level page/block tools in the sibling list.

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 clear context: every section is optional, `where` scopes the whole report, and it routes the agent to notion_create_chart for refreshing images and notion_undo for trashing. It does not explicitly say when to prefer this over manually composing pages with notion_create_page/notion_insert_blocks, so no full exclusion set.

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

Deploy Server

Other Tools