Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_theme

Delete a content theme from your active brand. Provide the theme ID to permanently remove it and clean up your content structure.

Instructions

Delete a content theme from the active brand.

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": {
      "themeId": "<themeId>"
    },
    "name": "delete_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand ID (uses active brand if omitted)
themeIdYesTheme ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It states the delete action but does not indicate whether deletion is permanent, whether it affects associated content, or if special permissions are required. The one-line description leaves significant behavioral context unaddressed.

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 sentence that is front-loaded with the action and resource. It is concise and contains no filler or redundant wording, fully earning 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?

The description provides enough to know the tool deletes a content theme for the active brand, but lacks context on irreversibility, side effects on content that uses the theme, and any prerequisites. For a destructive operation, more contextual detail would be expected, though the tool's simplicity partially compensates.

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%, as both brandId and themeId have descriptions. The description adds minimal context by mentioning 'active brand', which is already clarified in the brandId schema. Therefore, the description provides little value beyond the schema, warranting the baseline score of 3.

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' with a clear resource 'content theme' and scope 'from the active brand'. It clearly distinguishes this from sibling tools like edit_theme or generate_themes, which handle modification and creation.

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 usage when deleting a content theme, but provides no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions or naming conflicting tools, such as edit_theme, which could modify instead of delete.

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