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

ghl-mcp-server-v2

by zackscriven

ghl_social_get_comment_list

Retrieve paginated comments for a social media post or comment thread, with sorting, keyword search, date range, and connected-account filters to review and manage replies.

Instructions

List comments for a post or thread Paginated list of comments scoped to a post (parentId = postId) or a comment thread (parentId = commentId). Use skip/limit for pagination, sortBy for ordering, originIds to filter by connected account, and search for keyword search. Endpoint: POST /social-media-posting/comments/{platform}/list (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/comments.readonly

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>",
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_social_get_comment_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
platformYesSupported Comments Platforms
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / parentId / description
      Previous value: -"Parent ID — pass the Highlevel post ID (for replies under a specific post) or the Highlevel comment ID (for replies under a specific comment). Omit to list all top-level comments for the location filtered by `originIds`. Must be a valid 24-character Highlevel ID, not the native platform ID."New value: +"Parent ID — pass the internal post ID (for replies under a specific post) or the internal comment ID (for replies under a specific comment). Omit to list all top-level comments for the location filtered by `originIds`. Must be a valid 24-character internal ID, not the native platform ID."
    • addedInput schema / properties / body / title
      Added value: +"CommentsGetListBodyDTO"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior2/5

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

Adds genuinely useful operational context (endpoint, version header, sub-account token requirement, OAuth scope socialplanner/comments.readonly). However, that read-only framing conflicts with the annotations' readOnlyHint=false, giving the agent contradictory signals about whether the call mutates state.

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 purpose and scoping rule, then layers pagination/filtering hints and finally auth/endpoint metadata. Slightly repetitive with the schema on parameter explanations, but each block is short and earns its place.

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 paginated read list with no output schema, it supplies the scoping model, paging/filter knobs, auth prerequisites and endpoint — enough for correct invocation. The main omission is any hint about what a returned comment record contains or how it is ordered by default (sortBy default is only in the schema).

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%, so the schema already documents skip/limit/search/sortBy/parentId/originIds in detail. The description largely restates those parameter purposes rather than adding syntax or edge-case behavior beyond them.

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 ('List comments') and immediately distinguishes the two scopes it can serve: a post via parentId=postId vs a comment thread via parentId=commentId. An agent can identify this tool's exact function without reading the 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?

Explains when parentId should carry a post ID vs a comment ID, and clarifies via the schema that omitting it lists all top-level comments for the location. It doesn't explicitly name sibling alternatives, but none of the visible siblings list comments, so the routing gap is small.

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