Skip to main content
Glama
Sign In
docmost-community-mcp

docmost-community-mcp

by dilruwanm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

remove_page_label

Remove a label from a page by providing page ID and label ID. This helps maintain clean, organized wiki content.

Instructions

Remove a label from a page by label ID.

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": {
      "page_id": "<page_id>",
      "label_id": "<label_id>"
    },
    "name": "remove_page_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesPage UUID or slugId
label_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate this is a mutation (readOnlyHint: false) and not destructive (destructiveHint: false). The description adds the concrete semantics of removing a label association, but it does not explain side effects such as whether the label itself is deleted or whether removal is idempotent.

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?

A single clear sentence states the action, target, and required identifier with no filler. It is well-structured and front-loaded.

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 simple two-parameter mutation tool, the description plus schema provides enough information to call it correctly. Missing details like error behavior or confirmation that the label itself is not deleted are minor given the simple scope and available annotations.

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 only 50% because label_id lacks a description, but the phrase 'by label ID' supplies the semantic role for that parameter. page_id is already documented in the schema as 'Page UUID or slugId', so the description does not add much beyond confirming the label_id usage.

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 description states a specific action ('Remove'), a specific target ('a label from a page'), and the key input ('by label ID'). This clearly distinguishes it from sibling tools like add_page_labels and list_page_labels.

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

Usage Guidelines3/5

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

The description conveys when to use the tool implicitly by describing the operation, but it does not explicitly name alternatives or state when not to use it. An agent can infer usage from the verb, but no direct routing guidance is provided.

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