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

ghl-mcp-server-v2

by zackscriven

ghl_social_get_account

Read-onlyIdempotent

Retrieves the social media accounts and groups connected to a location, enabling you to identify available profiles and groups before planning or publishing posts.

Instructions

Get Accounts Get list of accounts and groups Endpoint: GET /social-media-posting/{locationId}/accounts (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/account.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>"
    },
    "name": "ghl_social_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds meaningful operational context: required Sub-Account token, OAuth scope, endpoint, and API version. It does not cover pagination or return format, but the auth and version details are valuable beyond the annotations.

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?

The definition is compact and front-loads the main purpose, then provides endpoint and auth details. The initial 'Get Accounts' line slightly duplicates the title, and source metadata is included, but overall it remains efficient.

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 read-only list endpoint with annotations covering safety and a fully described single parameter, the description provides sufficient context: resource purpose, auth requirements, OAuth scope, and endpoint version. No output schema exists, and the description does not need to explain return values in detail.

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% for the single locationId parameter, so the schema already does the documentation work. The description reinforces that locationId is part of the endpoint path, but adds little semantic detail beyond what the schema provides.

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 description states a specific read operation: retrieving accounts and groups for a location via the social posting endpoint. It is clear what resource is returned, but it does not explicitly distinguish this tool from related siblings such as ghl_social_get_oauth_accounts or platform-specific account lookups.

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

Usage Guidelines3/5

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

The description gives useful prerequisites—Sub-Account token and the socialplanner/account.readonly OAuth scope—but does not state when to choose this tool over alternatives like ghl_social_get_oauth_accounts. Usage is implied by the operation name rather than explicitly guided.

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