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

ghl-mcp-server-v2

by zackscriven

ghl_social_get_posts

Retrieve social media posts for a GoHighLevel sub-account with pagination and filters for post type, date range, status, and connected accounts.

Instructions

Get posts Get Posts Endpoint: POST /social-media-posting/{locationId}/posts/list (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/post.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": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_social_get_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. Changed10 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / limit / description
      Previous value: -"Maximum number of records to return"New value: +"Maximum number of records to return. Send as a numeric string — a JSON number is rejected."
    • changedInput schema / properties / body / properties / postType / description
      Previous value: -"Post Type must be one of the following values: - post, story, reel"New value: +"Post Type — one of: post, story, reel (enum taken from the field's own spec description). (Spec bug override 2026-08-27: upstream declares this as an empty object schema, rejecting every valid string.)"
    • addedInput schema / properties / body / properties / postType / enum
      Added value: +[
      +  "post",
      +  "story",
      +  "reel"
      +]
    • removedInput schema / properties / body / properties / postType / example
      Removed value: -"post"
    • changedInput schema / properties / body / properties / postType / type
      Previous value: -"object"New value: +"string"
    • changedInput schema / properties / body / properties / skip / description
      Previous value: -"Number of records to skip for pagination"New value: +"Number of records to skip for pagination. Send as a numeric string — a JSON number is rejected."
    • removedInput schema / properties / body / required
      Removed value: -[
      -  "skip",
      -  "limit",
      -  "fromDate",
      -  "toDate",
      -  "includeUsers"
      -]
    • addedInput schema / properties / body / title
      Added value: +"SearchPostDTO"
    • 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

B3/5.0
Behavior4/5

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

Adds real operational detail beyond annotations: the call is an HTTP POST to /social-media-posting/{locationId}/posts/list with a v3 version header, which explains why readOnlyHint=false despite being a read. It also discloses the required Sub-Account token and the socialplanner/post.readonly OAuth scope. It stops short of describing pagination behavior or result shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two lines ("Get posts" / "Get Posts") are pure duplication with zero informational value. The remaining endpoint/auth lines are compact and useful, and the whole thing is short, but it is metadata-first rather than front-loading what the tool actually returns.

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 2-parameter tool with a nested 8-field body and no output schema, the description covers invocation prerequisites adequately but leaves gaps an agent would want: what a returned post record contains, default result volume, and how this differs from the single-post getter. 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 coverage is 100%, including a nested SearchPostDTO with per-field descriptions and examples, so the schema already carries the parameter burden. The description only adds that locationId behaves as a Sub-Account token; it says nothing about the filters (type, postType, accounts, date range) or the numeric-string quirk for skip/limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource ("Get posts") plus the endpoint path make clear this lists social-planner posts for a location, but the wording restates the tool name almost verbatim and never distinguishes it from the singular sibling ghl_social_get_post. An agent must infer from the endpoint that this is a filtered list/search rather than a single-record fetch.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative tool is named, even though ghl_social_get_post, ghl_social_fetch_calendar_list and ghl_social_get_statistics sit adjacent in the same namespace. The only guidance given is a prerequisite (Sub-Account token, OAuth scope), which is authorization context rather than usage selection.

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