Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_account

DestructiveIdempotent

Deletes a social media account and removes it from its group using the account ID and location ID, enabling cleanup of disconnected or unwanted social profiles.

Instructions

Delete Account Delete account and account from group Endpoint: DELETE /social-media-posting/{locationId}/accounts/{id} (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/account.write

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": {
      "locationId": "<locationId>",
      "id": "<id>"
    },
    "name": "ghl_social_delete_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId
userIdNoID of the user performing the disconnect. Recorded for auditing only; omit it and the account is still deleted.
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • removedInput schema / properties / companyId
      Removed value: -{
      -  "description": "Company ID",
      -  "type": "string"
      -}
    • addedInput schema / properties / id / example
      Added value: +"65fac446d599990d1313c1dd"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
    • changedInput schema / properties / userId / description
      Previous value: -"User ID"New value: +"ID of the user performing the disconnect. Recorded for auditing only; omit it and the account is still deleted."
    • addedInput schema / properties / userId / example
      Added value: +"sdfdsfdsfEWEsdfsdsW32dd"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, readOnly=false, and openWorld=true, so the safety profile is covered. The description adds useful operational context beyond annotations by specifying the endpoint, required token type, and OAuth scope, though it does not fully describe downstream effects such as what happens to associated posts.

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?

The description is front-loaded and efficient, with endpoint/auth details that matter for invocation. The repeated 'Delete Account' / 'Delete account' phrasing is slightly redundant but not materially verbose.

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?

Given a destructive mutation with annotations covering safety, a fully documented schema, and no output schema, the description is largely complete. It includes the endpoint and auth requirements, though it could say more about the exact scope of deletion.

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%, with all three parameters documented, including the optional userId audit field. The description reinforces the endpoint path parameters but adds no semantics beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Delete Account') and includes the DELETE endpoint path, making it clear that this removes a social-media account. It does not explicitly differentiate itself from nearby social-account tools, but the resource scope is still clear.

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?

Provides prerequisite context ('Requires a Sub-Account (location) token') and OAuth scope, which implies when the tool is usable. However, it does not state exclusions, alternatives, or when to choose account deletion versus other social-management 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