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

ghl-mcp-server-v2

by zackscriven

ghl_social_bulk_delete_planner_posts

Delete multiple social planner posts by ID in one request (max 50) to clear large volumes of posts from the platform database.

Instructions

Bulk Delete Social Planner Posts Deletes multiple posts based on the provided list of post IDs. This operation is useful for clearing up large numbers of posts efficiently.

Note:

1.The maximum number of posts that can be deleted in a single request is '50'.

2.However, It will only get deleted in the platform database but still it is recommended to be cautious of this operation. Endpoint: POST /social-media-posting/{locationId}/posts/bulk-delete (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>",
      "body": "<body>"
    },
    "name": "ghl_social_bulk_delete_planner_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
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 / body / properties / postIds / description
      Previous value: -"Requested Results"New value: +"Post identifiers to delete. Each is either a 24-char post id or a 40-char native post id."
    • addedInput schema / properties / body / title
      Added value: +"DeletePostsDto"
    • changedInput schema / properties / locationId / description
      Previous value: -"Path parameter (inferred from the URL template; the official spec omits its declaration)."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

B3.4/5.0
Behavior3/5

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

It adds real behavioral context beyond the annotations: a hard limit of 50 posts per request, the fact that deletion is confined to the platform database, the required Sub-Account token, and the OAuth scope socialplanner/post.write. However, the cautionary note sits awkwardly against destructiveHint=false, and it never states what happens if some IDs in the list are invalid or whether the call is all-or-nothing.

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 core action is front-loaded in the first sentence, and the numbered notes are scannable. There is minor filler ("useful for clearing up large numbers of posts efficiently", raw endpoint/scope metadata), but nothing that buries the essential facts.

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 destructive batch mutation with a nested body object and no output schema, the description covers the limit and the auth requirement but omits response/partial-failure behavior and any confirmation guidance for an irreversible-feeling operation. Adequate, not complete.

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 schema already documents postIds (24-char post id or 40-char native post id) and locationId (Sub-Account ID). The description only reiterates "list of post IDs" and adds the batch size ceiling, so it does not meaningfully extend parameter meaning 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 verb (bulk delete) and a specific resource (Social Planner posts), plus the mechanism (a provided list of post IDs). It is clear what the tool does, but it never names the single-post sibling ghl_social_delete_post as the alternative, so sibling differentiation is left to the agent.

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?

"Useful for clearing up large numbers of posts efficiently" implies the bulk use case, but there is no explicit when-to-use / when-not-to-use guidance and no pointer to ghl_social_delete_post for single deletions. The 50-post cap indirectly signals a batch threshold, which is the only selection hint.

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