GHL MCP Server

List Connected Social Accounts

ghl_list_social_accounts

Read-onlyIdempotent

Get a complete list of social media accounts connected to a GoHighLevel location, including Facebook, Instagram, and Google. Use this tool to view all integrated social profiles at once.

Instructions

Get all connected social media accounts (Facebook, Instagram, Google, etc.).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_list_social_accounts"
  }
}

Input Schema

Name	Required	Description	Default
`locationId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds context about the types of accounts (Facebook, Instagram, Google) but does not disclose additional behavioral traits such as pagination, response format, or any quirks. This is acceptable given the annotation coverage.

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

Conciseness5/5

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

The description is a single, well-structured sentence that is front-loaded with the core purpose. It contains no unnecessary words and is appropriately sized for a simple list operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but the description lacks essential context such as the meaning of locationId, whether the response is paginated, and any special behaviors hinted by openWorldHint. With no output schema to clarify return shape, the description should provide more detail to fully inform the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one optional parameter (locationId) with no description, and the description does not mention it at all. With 0% schema description coverage, the description fails to compensate, leaving the parameter's purpose and usage completely unexplained.

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?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('all connected social media accounts'), listing examples that help distinguish it from sibling tools like ghl_list_social_posts. This makes the tool's identity unambiguous.

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 tool versus alternatives, no exclusions, and no mention of prerequisites or filters. While the description implies it is for retrieving social media accounts, it does not explain when to choose it over other list tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server