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

ghl-mcp-server-v2

by zackscriven

ghl_social_get_post

Read-onlyIdempotent

Retrieve a social media post by location and post ID from GoHighLevel Social Planner, returning post details for review, validation, or workflow use.

Instructions

Get post Endpoint: GET /social-media-posting/{locationId}/posts/{id} (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>",
      "id": "<id>"
    },
    "name": "ghl_social_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost Id. Accepts either a 24-character post id or a native platform post id (24-hex).
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • changedInput schema / properties / id / description
      Previous value: -"Post Id"New value: +"Post Id. Accepts either a 24-character post id or a native platform post id (24-hex)."
    • addedInput schema / properties / id / example
      Added value: +"65fac446d599990d1313c1dd"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real operational context not present in structured data: it requires a Sub-Account (location) token and the socialplanner/post.readonly OAuth scope, which is exactly what an agent needs before calling. It stops short of describing error behavior (e.g., post-not-found) or response shape.

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?

Four short lines, front-loaded with the action and the endpoint, then auth requirements. The version header and source JSON pointer are mildly low-value metadata but cost little and aid traceability.

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 read-only single-record fetch with full schema coverage and clear annotations, the description covers the essentials including auth scope. With no output schema, however, it never indicates what a returned post contains or how a missing id is signaled, leaving a real gap for an agent interpreting results.

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 itself notes the flexible id format (24-character post id or native platform post id). The description adds no parameter-level meaning beyond the endpoint template that already shows locationId and id as path segments, so baseline 3 applies.

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 name-plus-endpoint pair ('Get post' / GET /social-media-posting/{locationId}/posts/{id}') makes clear this retrieves a single social post by id, which is more specific than the bare title. It does not, however, name or contrast with siblings like ghl_social_get_posts (list) or ghl_social_get_csv_post, so an agent must infer the distinction from naming alone.

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?

There is no statement of when to use this versus ghl_social_get_posts, ghl_social_get_csv_post, or ghl_social_edit_session paths. The only contextual information given is authentication prerequisites, not selection guidance.

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