PostKing MCP Server

approve_post

Approve a draft post and schedule it for a future time by providing the post ID and an ISO 8601 UTC datetime.

Instructions

Approve and schedule a draft post. Requires a future datetime. The scheduledAt must be an ISO 8601 UTC datetime, e.g. 2026-03-11T09:00:00Z. After approving, the post status becomes 'scheduled'.

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": {
      "postId": "<postId>",
      "scheduledAt": "<scheduledAt>"
    },
    "name": "approve_post"
  }
}

Input Schema

Name	Required	Description
`postId`	Yes	Post ID to approve
`timezone`	No	User timezone, e.g. 'America/New_York'
`scheduledAt`	Yes	Future ISO 8601 UTC datetime to post at

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden and does disclose key behaviors: requires a future datetime, validates ISO 8601 UTC format, and changes the post status to 'scheduled'. However, it doesn't discuss error handling, prerequisites (e.g., whether the post must already be in draft status), or reversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three focused sentences, each adding value: what it does, the requirement, and the outcome. The description is well-structured and free of redundancy, though it could arguably be condensed further.

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 simple state-transition tool with no output schema, the description covers the essential aspects: action, required input constraint, and resulting state. It omits only edge-case details like error behavior or prerequisite validation, which are not critical for a low-complexity tool.

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 parameters are already well-documented. The description adds an example and clarifies that the datetime must be future and UTC, which is consistent with the schema's own descriptions but does not add significant new semantic information beyond reinforcing the format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Approve and schedule a draft post') and the resource ('draft post'), and specifies the resulting status change. However, it does not explicitly distinguish this tool from sibling tools like schedule_post or reschedule_post, so it is clear but not fully differentiated.

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?

Usage is implied through the draft post context and the requirement for a future datetime, but no explicit guidance is given on when to choose this over schedule_post or other scheduling tools. The description mentions the required format but doesn't address alternative workflows.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server