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

ghl-mcp-server-v2

by zackscriven

ghl_contact_remove_followers

DestructiveIdempotent

Removes specified followers from a contact in GoHighLevel by submitting a contact ID and user IDs, enabling targeted updates to who follows that contact.

Instructions

Remove Followers Endpoint: DELETE /contacts/{contactId}/followers (Version header: v3; source: v3/contacts-v3.json) OAuth scopes: contacts.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": {
      "contactId": "<contactId>",
      "body": "<body>"
    },
    "name": "ghl_contact_remove_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
contactIdYesContact Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"FollowersDTO"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful operational context the annotations lack: the required contacts.write scope and the v3 version header. It does not disclose what happens to followers not listed in the array, i.e. whether this is a full-list replacement or a partial removal.

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?

Four compact lines with the action front-loaded, followed by endpoint, version and scope metadata; no filler. The 'Remove Followers' title merely repeats the tool name, but that costs almost nothing.

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 destructive, open-world mutation with nested body params and no output schema, the essential call mechanics (endpoint, scope, idempotency via annotations) are present. However, the key behavioral question for this operation, whether the supplied followers array replaces the existing set or is subtracted from it, is left unanswered.

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%, so both contactId and body.followers are documented in the schema, which sets the baseline at 3. The description adds nothing about the array semantics, which is unfortunate because the schema's own wording ('follow or unfollow') is ambiguous for a remove-only endpoint.

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?

States a specific verb and resource ('Remove Followers') and backs it with the concrete endpoint DELETE /contacts/{contactId}/followers, so an agent can tell it apart from ghl_contact_add_followers without opening the schema. It stops short of explicitly naming that sibling as the inverse operation.

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?

The description never says when to use this rather than ghl_contact_add_followers or ghl_contact_update, nor does it state any precondition beyond the OAuth scope. The endpoint line implies a contact-scoped mutation but leaves usage inference entirely to the agent.

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