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

ghl-mcp-server-v2

by zackscriven

ghl_social_set_accounts

Sets the social media accounts a CSV import will publish posts to, linking account IDs for the specified location.

Instructions

Set Accounts Set social media accounts for a CSV import to publish posts to Endpoint: POST /social-media-posting/{locationId}/set-accounts (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/csv.write

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_set_accounts"
  }
}

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. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"SetAccountsDTO"
    • 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

A3.6/5.0
Behavior4/5

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

Annotations already declare the mutation/non-destructive/non-idempotent profile, and the description adds genuinely new operational context: the endpoint path, the v3 version header, the requirement for a Sub-Account (location) token, and the required OAuth scope socialplanner/csv.write. It stops short of saying whether accounts are replaced or appended or whether prior assignments are lost, which would matter for a non-idempotent setter.

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?

Purpose is front-loaded and the metadata lines are clearly sequenced (endpoint, auth, scope). The '(Version header: v3; source: v3/social-planner-v3.json)' provenance note is spec bookkeeping rather than agent-relevant information, which is the only real waste.

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 mutation with a rich nested body and no output schema, the description covers auth and endpoint but leaves the lifecycle unexplained: what state the CSV import must be in, whether set-accounts must precede ghl_social_csv_finalize, and what the caller gets back. Those are the questions an agent actually needs answered before invoking it.

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 all six nested body fields (userId, approver, fileName, filePath, rowsCount, accountIds, csvFileType) are documented in the schema, so the schema does the heavy lifting. The description only reaffirms locationId as the Sub-Account ID via the endpoint template and adds no format or constraint detail beyond it, which is the baseline 3 case.

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 verb and resource: assign social media accounts to a CSV import so posts can be published to them, plus the concrete endpoint POST /social-media-posting/{locationId}/set-accounts. That is enough to distinguish it from generic account tools like ghl_social_attach_instagram_page_group, though it never names the CSV siblings (ghl_social_csv_upload, ghl_social_csv_finalize) it most obviously overlaps with.

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 phrase 'for a CSV import' implies this is a step in the CSV posting pipeline, but there is no explicit when-to-use, no ordering guidance relative to csv_upload/csv_finalize, and no exclusions. The agent must infer its place in the workflow from the sibling names.

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