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

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_like

DestructiveIdempotent

Removes a like from a comment using its internal comment ID, covering top-level comments, replies, and replies-to-replies on Facebook, LinkedIn, Community, TikTok, and Bluesky.

Instructions

Unlike a comment Remove a like from a comment by its internal comment ID (the _id returned by the list-comments endpoint — not the native platform ID).

Works for any comment level — top-level comments, replies, and replies-to-replies. Supported platforms: Facebook, LinkedIn, Community, TikTok, Bluesky. Instagram is not supported (passing instagram returns 400). Endpoint: DELETE /social-media-posting/comments/{platform}/{id}/like (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/comments.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": {
      "platform": "<platform>",
      "id": "<id>",
      "locationId": "<locationId>"
    },
    "name": "ghl_social_delete_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesInternal comment ID — the `_id` returned by the list-comments endpoint (`POST /comments/{platform}/list`). Not the native platform comment ID. Works for any comment level: top-level comments, replies, and replies-to-replies.
platformYesPlatform that supports liking / unliking comments (Instagram is not supported)
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / id / description
      Previous value: -"Highlevel comment ID — the `_id` returned by the list-comments endpoint (`POST /comments/{platform}/list`). Not the native platform comment ID. Works for any comment level: top-level comments, replies, and replies-to-replies."New value: +"Internal comment ID — the `_id` returned by the list-comments endpoint (`POST /comments/{platform}/list`). Not the native platform comment ID. Works for any comment level: top-level comments, replies, and replies-to-replies."
  2. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the auth requirement (Sub-Account/location token), the OAuth scope socialplanner/comments.write, and the concrete failure mode for Instagram (400). It adds no detail on what happens for an already-unliked comment, but idempotentHint=true already covers that.

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?

Key constraint (ID type) is front-loaded and each subsequent sentence carries a distinct fact: comment-level scope, platform matrix, endpoint, auth. The endpoint/version/source line is operational padding but not a major detractor.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter delete with no output schema, the definition supplies everything needed to call it correctly: which ID form, which platforms, which auth context, and which failing input to avoid.

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 coverage is 100% and the schema already documents the ID semantics and the platform enum, so the description largely repeats rather than extends it. The platform-support note adds a small amount of meaning over the enum by explaining the omission of Instagram.

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?

States a specific verb+resource ('Unlike a comment', 'Remove a like from a comment') and pins the exact identifier it operates on (internal `_id`, not the native platform ID). An agent can distinguish it from the sibling ghl_social_create_like without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames the operation context: works at any comment level and lists supported platforms with the explicit exclusion 'Instagram is not supported (passing instagram returns 400)'. It does not explicitly route to the counterpart create-like tool, so the alternative is implied rather than named.

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