Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_account

DestructiveIdempotent

Permanently delete a social media posting account from GoHighLevel to revoke its access and remove it from your account.

Instructions

Delete Account Delete account and account from group Endpoint: DELETE /social-media-posting/{locationId}/accounts/{id} (Version header: v3; source: v3/social-planner-v3.json)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId
userIdNoUser ID
companyIdNoCompany ID
locationIdYesLocation Id
Behavior2/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds minimal behavioral context ('Delete account and account from group') but does not explain permanence, side effects, or required permissions. Beyond annotations, the description adds little value regarding behavior.

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?

The description is very short (two sentences plus endpoint) but includes redundant content: 'Delete Account' repeats the title. The endpoint detail is useful for developers but not semantically helpful for an AI agent. It is not concise in a targeted way.

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?

No output schema exists, and the description does not explain the return value or clarify if the deletion is permanent or if there are dependencies. For a destructive action, the description lacks sufficient context for full agent understanding.

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 already documents all parameters adequately. The description does not add any additional meaning or usage tips beyond what is in the schema, meeting baseline expectations.

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 it deletes an account and an account from a group, which combined with the tool name 'ghl_social_delete_account' and endpoint '/social-media-posting/{locationId}/accounts/{id}' clearly indicates it deletes a social media posting account. This distinguishes it from ad platform account deletes (e.g., ghl_ad_fb_account_delete) that appear in sibling tools.

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 explicit guidance on when to use this tool versus alternatives, no prerequisites or conditions mentioned. The agent receives no help in deciding between this and other account deletion tools.

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