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

ghl-mcp-server-v2

by zackscriven

ghl_social_attach_facebook_page_group

Attach a Facebook page to a specified GoHighLevel location and social account for page-based posting and management.

Instructions

Attach facebook pages Endpoint: POST /social-media-posting/oauth/{locationId}/facebook/accounts/{accountId} (Version header: 2021-07-28; source: social-media-posting.json)

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>",
      "accountId": "<accountId>",
      "body": "<body>"
    },
    "name": "ghl_social_attach_facebook_page_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
accountIdYesAccount Id
locationIdYesAccount Location Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / type / description
      Added value: +"Account type, e.g. 'page'. (Spec bug override 2026-08-27: upstream declares this as an empty object schema. No enum documented; 'page' is the spec example.)"
    • removedInput schema / properties / body / properties / type / example
      Removed value: -"page"
    • changedInput schema / properties / body / properties / type / type
      Previous value: -"object"New value: +"string"
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the write/non-idempotent profile is covered. The description adds only the HTTP method and API version header, which corroborates the write behavior but does not explain side effects, whether re-attaching is safe, or what state changes on the location's social accounts.

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?

It is short and front-loaded, but the parenthetical provenance ("source: social-media-posting.json") is low-value metadata while a sentence explaining the attach action is absent. Length is fine; the allocation of words is not.

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?

With annotations covering the safety profile and a fully documented nested schema despite no output schema, the main gap is an explanation of the effect of attaching. That gap is real but moderate given the rich structured fields available.

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% and all three parameters (locationId, accountId, body) are documented in the schema, including nested body fields, so the description needs little. It adds no meaning beyond the schema – notably it never explains the relationship between the path accountId and the body's originId/type fields.

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 description says "Attach facebook pages" plus the concrete endpoint POST /social-media-posting/oauth/{locationId}/facebook/accounts/{accountId}, so the verb and resource are identifiable. However, the phrasing is nearly a restatement of the tool name/title and never clarifies what 'attach' means operationally (linking a page/group to a location for posting).

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 guidance on when to use this versus the closely-named sibling ghl_social_get_facebook_page_group (list/discover) or ghl_social_attach_oauth_accounts. No prerequisites, such as an existing OAuth connection or required account type, are stated.

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