Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

disconnect_social_account

Remove a social account from your brand by specifying its account ID. Use this action to unlink profiles that are no longer needed.

Instructions

Disconnect a social account by its account ID.

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": {
      "accountId": "<accountId>"
    },
    "name": "disconnect_social_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand ID (uses active brand if omitted)
accountIdYesSocial account ID to disconnect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. 'Disconnect' implies a destructive/mutating action, but the description does not mention consequences such as token invalidation, whether the action is reversible, or required permissions. This is a significant gap for a destructive tool.

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 that states the essential operation without redundancy. It is appropriately concise for the tool's simplicity, with zero wasted words.

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?

For a simple two-parameter tool, the description is partially complete. It conveys the core action but lacks context such as consequences, prerequisites, or when to use it. Given the absence of annotations, the description should have disclosed more behavior to be fully complete, but the simplicity of the tool keeps this from being a major failure.

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 description coverage is 100%, so the baseline is 3. The description mentions the account ID, but this adds no value beyond the schema's own description. It does not mention the optional brandId parameter or clarify any parameter semantics further, so it neither enhances nor harms the schema information.

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 (disconnect) and the resource (social account), with the specific identifier (account ID). This uniquely distinguishes it from sibling tools like check_social_accounts or generate_connect_link, which serve different purposes.

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?

The description provides no guidance on when to use this tool, prerequisites, or how it differs from alternatives. It simply states the function without context, leaving the agent without enough information to choose this over other social account operations.

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