Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

social_media_posting_delete_account

DestructiveIdempotent

Remove a social media posting account from GoHighLevel using its ID. Provide the account ID and optional user, company, or location to delete the connection.

Instructions

Delete Account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId
userIdNoUser ID
companyIdNoCompany ID
locationIdNoLocation Id Defaults to GHL_LOCATION_ID when omitted.
Behavior2/5

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

The description adds nothing beyond the annotations (destructiveHint, idempotentHint). It doesn't clarify consequences like permanence, effect on linked posts, or whether the action is reversible. There is no contradiction with annotations, but also no added behavioral context.

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 only two words, which is under-specification rather than effective conciseness. It lacks structure and fails to communicate essential information, making it a fragment rather than a useful sentence.

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

Completeness1/5

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

For a destructive tool with no output schema, the description is completely inadequate. It omits what happens on deletion, return values, or any caveats. The agent must rely entirely on the name and schema, which is insufficient for safe and correct invocation.

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?

The schema provides 100% coverage with descriptions for all four parameters, including the default behavior of locationId. The description itself adds no parameter detail, but since the schema already handles this, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete Account' is essentially a restatement of the tool name, providing no additional specificity about what type of account is deleted or what the deletion entails. It doesn't differentiate from sibling tools like delete_post or delete_csv, leaving the agent to infer meaning from the name alone.

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 is provided on when to use this tool versus alternatives. The description doesn't mention scenarios, prerequisites, or exclusions, leaving the agent without context for making a correct selection among the many social media posting 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/AIWerk/mcp-server-ghl'

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