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

ghl-mcp-server-v2

by zackscriven

ghl_opportunity_add_followers

Adds up to 10 user IDs as followers to a GoHighLevel opportunity so relevant users can track its updates.

Instructions

Add Followers Endpoint: POST /opportunities/{id}/followers (Version header: v3; source: v3/opportunities-v3.json) OAuth scopes: opportunities.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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "ghl_opportunity_add_followers"
  }
}

Input Schema

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

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 readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered. The description adds genuinely useful context beyond that — the required OAuth scope opportunities.write and the v3 version header — but says nothing about whether adding is additive or replaces the existing follower set, which is the key behavioral unknown.

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?

Three terse lines, front-loaded with the action and followed by endpoint, version and scope metadata; no filler prose. It is efficient but reads like raw spec extraction rather than an explanation, which slightly limits usefulness.

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 two-parameter mutation with full schema coverage and no output schema, the definition is minimally adequate. It is missing the one thing an agent would actually want to know before calling: whether the supplied follower list is merged with or replaces existing followers, and what the response confirms.

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%: the id is documented as "Opportunity Id" and the followers array is documented with a max of 10. The description adds nothing about parameter format or semantics, so the baseline 3 applies.

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 gives a specific verb and resource ("Add Followers" on POST /opportunities/{id}/followers), and the endpoint path pins the resource to an opportunity, distinguishing it from ghl_contact_add_followers. It never names the obvious counterpart ghl_opportunity_remove_followers, so sibling differentiation is left to the tool name rather than stated in prose.

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?

There is no when-to-use or when-not-to-use guidance at all. The agent must infer from the name and endpoint that this attaches users as followers to an opportunity, and there is no mention of the remove_followers sibling that would be the natural alternative.

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