Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

knowledge_delete

Soft-delete a knowledge-base item to remove it from knowledge listings without permanent deletion. Deactivates the item instantly; this action cannot be undone through the API.

Instructions

Soft-delete a knowledge-base item. The item is deactivated (isActive=false) and no longer appears in knowledge_list. This action is not reversible via the API.

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": {
      "itemId": "<itemId>"
    },
    "name": "knowledge_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesKnowledgeBase item ID to soft-delete.
brandIdNoBrand ID (defaults to active brand)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly explains that the item is soft-deleted (isActive=false), disappears from knowledge_list, and cannot be reversed via the API. This is rich, transparent detail beyond what the schema or name provide.

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 three concise sentences, front-loaded with the verb 'soft-delete', and each sentence provides a necessary piece of information: what it does, the effect, and irreversibility. There is no redundancy or fluff.

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?

Given the tool's low complexity (2 params, no output schema), the description is complete. It explains the primary action, the observable effect (isActive=false and removal from list), and an important constraint (irreversibility). No additional information is needed for an agent to invoke it 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?

The input schema covers 100% of the parameters with meaningful descriptions (itemId and brandId, including brandId's default behavior). The description adds no additional parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the verb 'soft-delete' and the resource 'knowledge-base item', and distinguishes it from sibling knowledge_* tools by specifying the effect (isActive=false, no longer appears in knowledge_list). It also notes irreversibility, which reinforces its unique purpose.

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?

The description provides clear context on the tool's behavior and consequences: it's a soft-delete, deactivates the item, and is irreversible. While it doesn't explicitly name alternatives, the context is sufficient for an agent to decide when to use this tool.

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