Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

disable_weekly_schedule

Pause a weekly content schedule without deleting it. Use this action to temporarily stop scheduled posts, then re-enable the schedule later when ready.

Instructions

Pause the weekly content schedule without deleting it. Re-enable later with enable_weekly_schedule.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "disable_weekly_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand ID (defaults to active brand)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It explicitly states the non-destructive nature ('without deleting it') and reversibility ('Re-enable later'), which are key behavioral traits. It does not mention side effects or permissions, but for a simple pause operation, the disclosure is sufficient.

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?

Two concise sentences, front-loaded with the action verb. No wasted words; every word adds value.

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

Completeness5/5

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

The tool is simple: one optional parameter, no output schema, and a straightforward action. The description fully explains the purpose and the relation to enable_weekly_schedule, making it complete for its simplicity.

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 only parameter (brandId) is fully described in the schema with 'Brand ID (defaults to active brand)', so schema coverage is 100%. The description adds no additional parameter context, which is acceptable given the high 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 (pause) and the resource (weekly content schedule), and explicitly contrasts with deletion ('without deleting it'), distinguishing it from the sibling tool delete_weekly_schedule.

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 implies when to use it ('Pause... without deleting it') and names the re-enable alternative (enable_weekly_schedule). However, it does not explicitly mention delete_weekly_schedule as the alternative for permanent removal, though the contrast with deletion is implicit.

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