nc-mcp-server

create_collective_page

Add a new Markdown page to a collective under a parent page; top-level pages require the landing page ID.

Instructions

Create a new page in a collective.

Pages are Markdown documents organized in a tree structure. Every page must have a parent — use the landing page ID as parent for top-level pages.

Args: collective_id: The numeric collective ID. parent_id: Parent page ID. Use the landing page ID from get_collective_pages for top-level pages. title: Title of the new page (required). content: Optional Markdown text for the page.

Returns: JSON object with the created page details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`title`	Yes
`content`	No
`parent_id`	Yes
`collective_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.9.0Oct 1, 2026
- addedInput schema / properties / content
```
Added value: +{
+  "default": "",
+  "title": "Content",
+  "type": "string"
+}
```
First observedv0.7.0Sep 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is known. The description adds the structural parent requirement and notes the return type, but does not mention auth/permission needs or side effects beyond what annotations convey.

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 core action, then structured with Args and Returns sections. Efficient overall, though the 'Returns' line partly duplicates the output schema and could be trimmed.

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 4-param creation tool with an output schema present, the description covers the action, the structural constraint, and each parameter. It is largely self-sufficient, missing only permission/error expectations, which the output schema and annotations partially offset.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the burden and does so: it documents collective_id (numeric collective ID), parent_id (with the non-obvious landing-page-ID rule), title (required), and content (optional Markdown). Only omission is that the underlying types/defaults are left to the schema.

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

Purpose4/5

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

States a specific verb+resource ('Create a new page in a collective') and adds a useful conceptual model (Markdown documents in a tree structure). It is clearly distinguishable from sibling read/mutation tools like update_collective_page and get_collective_pages, though it does not name them explicitly.

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 a concrete usage rule: every page must have a parent, and top-level pages should use the landing page ID from get_collective_pages. This routes the agent usefully, but it offers no explicit when-not or alternative-tool guidance (e.g., vs update/move).

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

Deploy Server