Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

edit_theme

Update a content theme's title or content instructions. Modify existing theme details to keep brand messaging current.

Instructions

Edit an existing content theme's title or content instructions.

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": "edit_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title for the theme
brandIdNoBrand ID (uses active brand if omitted)
contentNoNew content instructions for the theme
themeIdYesTheme ID to edit

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?

No annotations are provided, so the description carries the full burden. It only says 'edit,' without disclosing update semantics (e.g., partial vs full update), whether omitted fields are preserved, or any permission requirements. This is insufficient for a mutation tool.

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, clear sentence that efficiently conveys the tool's purpose without unnecessary detail.

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 covers the high-level purpose but omits important behavioral details like partial-update behavior and return value. Given the tool's simplicity and the schema's completeness, it's minimally sufficient but not comprehensive.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description mentions 'title or content instructions' but does not add extra meaning beyond the schema's field descriptions, nor does it elaborate on brandId or themeId.

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: editing an existing content theme's title or content instructions. This distinguishes it from theme creation or deletion tools (e.g., delete_theme, generate_themes) and specifies the mutable fields.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The word 'existing' implies the theme must already be created, but there is no mention of using list_themes to find theme IDs or generate_themes to create new ones.

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