Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

seo_roadmap_delete

Delete an SEO roadmap item permanently. Provide the item ID and confirm deletion to remove outdated entries from your content plan.

Instructions

Permanently delete a roadmap item. Pass confirm: true to proceed — this is irreversible.

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>",
      "confirm": "<confirm>"
    },
    "name": "seo_roadmap_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesRoadmap item ID to delete
brandIdNoBrand ID (defaults to active brand)
confirmYesMust be true to confirm deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that the deletion is permanent and irreversible, and explicitly requires a confirmation flag. This is key behavioral information. However, it does not mention potential cascading effects, permissions, or return behavior, but the core destructive nature is clearly stated.

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 two short sentences, front-loaded with the action and permanence, and includes the critical confirmation requirement. Every word earns its place with no redundancy.

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 delete tool with 3 parameters and no output schema, the description plus schema provide the essential context: what is deleted, how to confirm, and irreversibility. The brandId default is documented in the schema. It could mention what happens after deletion (e.g., return value), but that is not critical for a delete operation.

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 has 100% description coverage for all parameters, so the schema already explains itemId, brandId, and confirm. The description adds minimal extra meaning beyond confirming that confirm: true is required and the action is irreversible. This aligns with the baseline for high schema coverage.

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 ('delete'), the specific resource ('roadmap item'), and the permanence ('Permanently'). It distinguishes itself from sibling tools like seo_roadmap_edit, seo_roadmap_get, and seo_list_roadmap by indicating a destructive action.

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 implies the tool is for deleting roadmap items when deletion is intended, but it does not provide explicit guidance on when not to use it or mention alternatives (e.g., seo_roadmap_edit for reversible changes). The instruction to pass confirm: true is more about invocation than usage context.

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