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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_user_subscription_change

Processes admin- or agent-initiated subscription changes for a contact, including custom actions and resubscribe-all requests; creates legal forms for user resubscribe actions.

Instructions

[LEGACY FALLBACK — this endpoint is no longer in the live v3 docs (checked 2026-10-28) but is still served under the legacy Version header. Expect removal; prefer a current equivalent.] User Subscription Change Process subscription change initiated by a user (admin/agent). Supports individual custom subscription changes and resub all functionality. Legal forms are automatically created for user-initiated resubscribe actions on custom subscriptions. Endpoint: POST /conversations/preferences/unsubscriptions/user-change (Version header: 2021-04-15; source: conversations.json)

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": {
      "body": "<body>"
    },
    "name": "ghl_conversation_user_subscription_change"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, open-world mutation. The description adds genuinely non-obvious behavior beyond that: legal forms are automatically created for user-initiated resubscribe actions on custom subscriptions, and a specific Version header is required. It omits the response shape, but the side-effect disclosure is meaningful value-add.

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?

The deprecation warning is front-loaded in brackets and the rest is a compact purpose-plus-endpoint block with source metadata. Slightly dense with scaffolding (Endpoint, Version, source) but each line carries routing or provenance value.

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

Completeness4/5

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

For a nested-body mutation with no output schema, the description covers the key risk (auto-created legal forms), the required version header, and deprecation status. Return values are unspecified, a minor gap given the operation is an action rather than a query.

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%, including nested subscription_action details, enum values, and worked examples, so the schema carries parameter meaning fully. The description adds only that resubscribe/resub_all actions require legal fields - a small increment. Baseline 3 is appropriate.

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+resource: "Process subscription change initiated by a user (admin/agent)" with the concrete endpoint POST /conversations/preferences/unsubscriptions/user-change. An agent can distinguish it from sibling reads like ghl_conversation_get_contact_unsubscription_status. It stops short of explicitly contrasting with those siblings, so not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The bracketed legacy warning gives strong when-to-use guidance: the endpoint is no longer in live v3 docs, removal is expected, and a current equivalent should be preferred. It does not name which sibling is the replacement, leaving the agent to infer the alternative, which keeps it below 5.

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