Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_blog_article

Permanently delete a blog article by providing its ID. Remove unwanted or outdated posts from your blog.

Instructions

Permanently delete a blog article.

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": {
      "articleId": "<articleId>"
    },
    "name": "delete_blog_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand ID (uses active brand if omitted)
articleIdYesBlog article ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does state the action is permanent, which is a critical safety trait. However, it does not mention permissions, cascading effects, or whether deletion is limited to certain article statuses, leaving some ambiguity.

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 a single sentence with no redundant words. It front-loads the core action and permanence, making it easy to scan. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete-by-ID operation, the description is minimally sufficient, especially with complete parameter documentation in the schema. However, it does not explain the return value, any restrictions on deletion, or what happens to associated data, so it is not fully complete.

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 100%, with both 'brandId' and 'articleId' documented in the input schema. The description adds no parameter-specific information beyond the schema, which is acceptable given complete coverage. Baseline of 3 applies.

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 uses a specific verb 'delete' and resource 'blog article', clearly distinguishing it from sibling delete tools like delete_publication or delete_asset. The word 'permanently' adds important context about the action's irreversibility.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as delete_publication, delete_post, or unpublishing. The description does not mention prerequisites like active brand or restrictions on article state (draft/scheduled/published).

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