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

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_post

DestructiveIdempotent

Deletes a social media post from a GoHighLevel sub-account by location ID and post ID, removing outdated or incorrect content from the social planner.

Instructions

Delete Post Endpoint: DELETE /social-media-posting/{locationId}/posts/{id} (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/post.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_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID of the post to retrieve, update, or delete. **Get Post IDs from:** [List Posts API](/social-media-posting/{locationId}/posts/list) — use the `_id` field from each post.
locationIdYesLocation ID (also known as Sub-Account ID) for the business location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • changedInput schema / properties / id / description
      Previous value: -"Post Id"New value: +"Post ID of the post to retrieve, update, or delete.\n\n**Get Post IDs from:** [List Posts API](/social-media-posting/{locationId}/posts/list) — use the `_id` field from each post."
    • addedInput schema / properties / id / example
      Added value: +"65fac446d599990d1313c1dd"
    • changedInput schema / properties / locationId / description
      Previous value: -"Location Id"New value: +"Location ID (also known as Sub-Account ID) for the business location."
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  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 flag destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real extra context the annotations cannot carry: the exact HTTP verb/path, API version header, and required OAuth scope and token type.

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?

Front-loaded with the action and endpoint, then only the auth facts. The provenance note ("source: v3/social-planner-v3.json") is mild boilerplate noise but occupies one short parenthetical.

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 two-parameter delete with full schema coverage and annotations covering destructiveness and idempotency, this is largely sufficient: the agent knows the endpoint, credentials, and scope. It does not say whether deletion is permanent or what happens to associated comments/likes, though annotations imply the destructiveness.

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% and the `id` param already documents how to obtain post IDs via the List Posts API, so the schema carries the semantics. The description only shows the parameter positions in the endpoint path, adding nothing beyond that.

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+resource ("Delete Post") and pins it with the exact DELETE endpoint and path parameters. It does not explicitly distinguish itself from near-siblings like ghl_social_bulk_delete_planner_posts or ghl_social_delete_csv_post, so an agent must infer this deletes a single planner post.

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?

The description gives prerequisites (Sub-Account/location token, socialplanner/post.write scope) but never states when to choose this over the bulk-delete or CSV-delete siblings, nor any warning about confirming before deletion.

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