nc-mcp-server

trash_collective_page

DestructiveIdempotent

Move a page to a collective's trash by specifying collective and page IDs. The page is soft-deleted and can be restored or permanently removed later.

Instructions

Move a page to the collective's trash.

The page is soft-deleted. Use restore_collective_page to undo, or delete_collective_page to permanently remove it. The landing page cannot be trashed.

Args: collective_id: The numeric collective ID. page_id: The numeric page ID.

Returns: Confirmation message.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collective_id": "<collective_id>",
      "page_id": "<page_id>"
    },
    "name": "trash_collective_page"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes
`collective_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description adds meaningful behavioral context: the page is soft-deleted, the action is reversible via restore, permanent removal requires a different tool, and the landing page is an invalid target. It even states that a confirmation message is returned, which is useful operational detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-structured: operation, soft-delete consequence, undo/permanent alternatives, constraint, args, and return value. Every sentence earns its place and the most important behavioral distinction is front-loaded.

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?

For a two-parameter mutation with an output schema and annotations already covering the destructive/idempotent nature, the description provides the essential lifecycle, constraints, and response information. Nothing critical is missing for an agent to select and invoke this tool 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 description coverage is 0%, so the description must compensate. It does label both required parameters and adds the landing-page restriction, but 'numeric collective ID' and 'numeric page ID' largely restate the schema titles and provide no additional constraints or guidance on how to obtain the IDs. This is adequate for simple ID parameters but not more.

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?

The opening sentence 'Move a page to the collective's trash' gives a specific verb and resource, and the description immediately clarifies that the action is a soft-delete. It also names related sibling operations restore_collective_page and delete_collective_page, making the tool's purpose easy to distinguish from permanent deletion.

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

Usage Guidelines5/5

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

The description explicitly explains the soft-delete behavior and tells the agent that restore_collective_page undoes the action while delete_collective_page permanently removes the page. It also calls out the landing-page restriction, giving clear conditions for when this tool can and cannot be used.

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

Deploy Server