Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

seo_bulk_delete_keywords

Delete multiple irrelevant SEO keywords in one call to clean up your keyword list. Soft-deletes rows by setting deletedAt, keeping them in the DB but filtering them out of all queries.

Instructions

Soft-delete N SeoScoredKeyword rows in one call (sets deletedAt; rows stay in the DB but are filtered out of all queries). Housekeeping op — not part of the main flow. Pass confirm: true to proceed. Use to clear out a batch of junk/irrelevant keywords the auto-pipeline missed, e.g. after filtering seo_list_keywords by relevanceMax.

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": {
      "keywordIds": "<keywordIds>",
      "confirm": "<confirm>"
    },
    "name": "seo_bulk_delete_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand ID (defaults to active brand)
confirmYesMust be true to confirm bulk soft-delete
keywordIdsYesKeyword IDs from seo_list_keywords

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full responsibility and clearly discloses the soft-delete behavior: rows stay in the DB but are filtered out of all queries. It also highlights the confirmation requirement ('Pass confirm: true'). Minor gaps remain around reversibility and response format, but the core behavior is transparent.

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 sentences long, front-loaded with purpose, then behavior, then usage. Every sentence adds value with zero wasted words.

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?

Given the tool's complexity (bulk delete, confirmation flag, soft-delete behavior) and lack of annotations/output schema, the description covers the essential aspects well. It does not explain return values or edge cases like idempotency, but these are not critical for a bulk delete operation with clear usage guidance.

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 100%, so the baseline is 3. The description adds slight context by mentioning 'keywordIds' are derived from seo_list_keywords, but does not significantly enrich the parameter understanding beyond the schema.

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 tool's function: 'Soft-delete N SeoScoredKeyword rows in one call' with specific behavior (sets deletedAt). It distinguishes this bulk operation from singular delete tools by emphasizing 'in one call' and 'Housekeeping op'.

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 explicit usage context: 'Housekeeping op — not part of the main flow' and a concrete example ('after filtering seo_list_keywords by relevanceMax'). However, it does not directly compare to the singular delete tool (seo_delete_keyword), leaving some ambiguity about when to prefer one over the other.

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