notion_list_templatesList a Notion database's page templates, including each template's name, ID, and default status, to find the correct template name or ID for creating pages.
List a database's page templates (name, id, which is the default). Use a name or id as notion_create_page's template.
| Name | Required | Description | Default |
|---|---|---|---|
| database | Yes | ||
| data_source_name | No |
Changes observed during successful MCP inspections.
v0.10.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond that by naming the returned fields (name, id, default), which matters since there is no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence with the purpose front-loaded and the downstream usage appended; no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only list tool with no output schema, the description usefully sketches the return shape and the consumer of that output. However, it leaves the second parameter undocumented, which is a real gap given 0% schema coverage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for two parameters. The description implies the `database` parameter via 'a database's page templates' but says nothing about `data_source_name` or the expected id/name format, so it fails to compensate for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (a database's page templates) and even enumerates the returned fields (name, id, default). No sibling tool covers templates, so it is unambiguous which tool to pick.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells the agent the follow-on action: feed a returned name or id into notion_create_page's `template` parameter, which implies when this tool is used. It does not state any when-not condition, but the workflow context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.