PostKing MCP Server

set_social_media_rules

Update a brand's social media content rules for a specific platform. Merge new settings into existing rules or replace them entirely.

Instructions

Update a brand's social media content rules for ONE platform. By default this MERGES your provided fields into the existing rules (send only what you want to change — other fields are preserved; arrays you provide replace the old array). Set replace=true to overwrite the entire platform ruleset. Valid platforms: linkedin, x/twitter, facebook, instagram, threads, general. Tip: call get_social_media_rules first to see current values.

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": {
      "platform": "<platform>",
      "rules": "<rules>"
    },
    "name": "set_social_media_rules"
  }
}

Input Schema

Name	Required	Description
`rules`	Yes	Partial or full ruleset to apply. Only provide the fields you want to change when merging.
`brandId`	No	Brand ID (uses active brand if omitted)
`replace`	No	Overwrite the entire platform ruleset instead of merging.
`platform`	Yes	The platform whose rules you want to update.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.7Aug 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description takes on the full burden. It discloses the default merge behavior, that arrays replace the old array, and that replace=true overwrites the entire ruleset. It doesn't cover every edge case (e.g., nested object merging, return value), but the key non-destructive vs. destructive behaviors are clear.

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 compact and front-loaded, using three sentences to convey the purpose, the merge behavior, the replacement option, and a helpful tip. No redundancies or filler words.

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 an update tool, the description covers the essential behavior, valid platforms, and a read-before-update tip. It doesn't mention return values or error conditions, but with no output schema and a relatively simple operation, this is acceptable. The only major ambiguity is whether nested objects are deep-merged, which could be clearer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already has 100% coverage for parameters, but the description adds value by explaining the practical implications: send only what you want to change and how array fields behave. It also clarifies the replace flag's effect beyond the schema's one-line description.

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 action (Update) and the resource (a brand's social media content rules) with a specific scope (for ONE platform). This distinguishes it from the sibling get_social_media_rules tool by explicitly positioning it as the update counterpart and listing valid platforms.

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?

It provides explicit usage context: merge vs. replace semantics, and the tip to call get_social_media_rules first to see current values. This gives the agent clear guidance on how to use the tool effectively and which sibling tool is complementary for reads.

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

Deploy Server