Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

schedule_blog_article

Schedule an existing blog article for future auto-publishing, including distribution to connected external platforms at the scheduled time.

Instructions

Schedule an existing blog article to auto-publish at a future date/time. scheduledAt must be a future ISO 8601 datetime. When the time arrives, the article publishes to the PostKing blog and auto-pushes to any connected external platforms flagged autoPublish. To publish immediately instead, use update_blog_article with status='published'.

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": {
      "articleId": "<articleId>",
      "scheduledAt": "<scheduledAt>"
    },
    "name": "schedule_blog_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand ID (uses active brand if omitted)
articleIdYesBlog article ID
scheduledAtYesISO 8601 datetime in the future, e.g. 2026-07-10T14:30:00Z, when the article should auto-publish

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses what happens when the scheduled time arrives: publishes to the PostKing blog and auto-pushes to external platforms flagged autoPublish. It also adds the constraint that scheduledAt must be future. No annotations exist, so the description carries the burden; it covers key behavioral points but does not mention cancellation or what the API returns.

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 sentences, front-loaded with the purpose, then key constraint, then behavioral effect, then alternative. No redundant or irrelevant content.

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 scheduling tool with no output schema, the description covers core behavior, timing constraint, side effects (auto-push), and alternative. It lacks details about success return value or how to manage the schedule, but is largely complete for typical usage.

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%, and the description adds only minimal param nuance (e.g., 'existing' article, future datetime) which is also encoded in the schema. The description does not significantly extend schema-provided semantics, so the baseline 3 applies.

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 opens with a clear, specific verb-resource pair: 'Schedule an existing blog article to auto-publish at a future date/time.' It clearly distinguishes from siblings by naming an alternative for immediate publishing (update_blog_article) and by specifying blog article rather than social posts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives a when-not-to-use condition and alternative: 'To publish immediately instead, use update_blog_article with status="published"'. This differentiates from the immediate-publish sibling and clarifies the intended use case for future scheduling.

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