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

ghl-mcp-server-v2

by zackscriven

ghl_social_create_like

Like a social media comment by its internal comment ID, supporting top-level comments, replies, and replies-to-replies across Facebook, LinkedIn, Community, TikTok, and Bluesky.

Instructions

Like a comment Like 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: POST /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_create_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.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing auth requirements (Sub-Account/location token), the OAuth scope socialplanner/comments.write, the underlying endpoint and version header, and a concrete failure mode (Instagram returns 400). This complements the non-readOnly, non-destructive, non-idempotent hints with actionable operational context.

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-loads the action and ID semantics before platform and auth notes, and each line carries useful information. Minor redundancy between the opening line and the title, and the endpoint/source metadata line is developer-facing rather than agent-facing.

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-required-param mutation with no output schema, the description covers the identifier source, platform support matrix, auth/prerequisite, and a named error case — everything an agent needs to invoke it correctly.

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%, so all three parameters are already documented in the schema, including the internal-vs-native ID distinction and the platform enum excluding Instagram. The description largely restates that rather than adding new semantic detail (e.g., no format constraints or behavior for a stale/invalid ID).

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 and resource ('Like a comment') plus the exact identifier semantics (internal `_id`, not the native platform ID). The scope statement distinguishes it from siblings like ghl_social_get_comment_list (source of the ID) and ghl_social_delete_like (the inverse operation).

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

Usage Guidelines5/5

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

Explicit about when it applies: any comment level (top-level, replies, replies-to-replies), and which platforms it covers versus the exclusion of Instagram (400 error). It also names the upstream endpoint that produces a valid `id`, so an agent knows the prerequisite call.

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