Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_social_attach_linkedin_page_profile

Attaches LinkedIn pages or profiles to a GoHighLevel location account by providing account, location IDs, and profile details.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
accountIdYesAccount Id
locationIdYesAccount Location Id
Behavior2/5

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

Annotations indicate a non-read-only, non-destructive write operation, which aligns with 'Attach'. However, the description provides no additional behavioral context beyond the endpoint URL, such as whether the action is idempotent, what the response contains, or any side effects.

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

Conciseness2/5

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

The description is very short but omits essential details. While it has no fluff, it is under-specified for a tool with required nested parameters and no output schema. Front-loading is minimal.

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?

Given the tool complexity (nested body, 3 required params, no output schema), the description is incomplete. It does not explain the concept of 'attaching', expected outcomes, or any preconditions. The endpoint detail is useful but not sufficient.

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%, so the schema itself documents parameters. The description includes the endpoint URL which reinforces the path parameters (locationId, accountId) but adds no semantic context for the nested body fields. The body description merely restates the schema source.

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 'Attach linkedin pages and profile', which is a specific verb and resource. The tool name includes the platform, distinguishing it from sibling tools for Facebook, Instagram, etc. However, it does not elaborate on what 'attach' entails (e.g., linking an account).

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use, or alternative tools. The sibling list includes other social attach tools, but no explicit comparison is made.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zackscriven/ghl-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server