Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

rewrite_text

Rewrite text using a voice profile or general writing rules. Adjust content for platform and brand voice to improve consistency and clarity.

Instructions

Rewrite text using a voice profile or general writing rules.

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": {
      "text": "<text>"
    },
    "name": "rewrite_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to rewrite
voiceNoVoice profile ID to apply
brandIdNoBrand ID (uses active brand if omitted)
platformNoPlatform context: x | linkedin | instagram | threads | facebook

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description must disclose behavior on its own. It does explain the main behavior (rewriting using voice or general rules), but it omits details about side effects, permissions, return format, or any rate limits. It adds only minimal context beyond the literal action.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core function and the two modes of operation.

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 tool is simple (4 parameters, no output schema, no annotations), so the description provides a reasonable high-level overview. However, it lacks usage context, does not clarify the vague 'general writing rules,' and gives no sense of what the tool returns, leaving some gaps.

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 input schema already covers all parameters with descriptions (100% coverage), so the baseline is 3. The description mentions 'general writing rules,' which is vague and doesn't map cleanly to any parameter (voice, brandId, platform), thus failing to add meaningful semantic value beyond the schema.

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 states a specific action ('Rewrite text') with a clear resource. It hints at two modes ('voice profile or general writing rules') which helps distinguish from a sibling like rewrite_with_voice, but it doesn't explicitly name alternatives.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus closely related tools like rewrite_with_voice or generate_text. There are no stated prerequisites, exclusions, or alternative tool references.

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