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

ghl-mcp-server-v2

by zackscriven

ghl_conversation_get_contact_unsubscription_status

Read-onlyIdempotent

Retrieve all subscription statuses for a contact or check a specific email address using contact and location IDs.

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.] Get Contact Unsubscription Status Get all subscription statuses for a contact (all emails or specific email) Endpoint: GET /conversations/preferences/unsubscriptions/status (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": {
      "locationId": "<locationId>",
      "contactId": "<contactId>"
    },
    "name": "ghl_conversation_get_contact_unsubscription_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail address (optional - if not provided, gets all emails for contact)
contactIdYesContact Id
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the critical invocation detail: it must be called with the Version header 2021-04-15 via the legacy stack, and the endpoint may disappear. It does not describe the response shape, but with no output schema that is a minor omission for a simple status read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The deprecation warning is front-loaded in brackets before the purpose, which is the right ordering for a risky tool, and the rest is three compact lines: title, behavior, endpoint. There is minor redundancy in repeating the title, but no wasted sentences.

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 two-required-param read with no nested objects and no output schema, the description covers purpose, endpoint, version header, and lifecycle status. The one real gap is that the recommended replacement is unnamed, which is exactly the information an agent needs before deciding to call it at all.

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%, and the description's only parameter-related statement ('all emails or specific email') restates the schema text for the optional email field. Nothing is added about contactId/locationId pairing or cross-location behavior, so the baseline 3 applies.

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

Purpose5/5

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

The description states a specific verb and resource ('Get all subscription statuses for a contact') plus the exact scope ('all emails or specific email'), and pins the underlying route GET /conversations/preferences/unsubscriptions/status. No sibling tool in the list covers subscription/unsubscription status, so it is unambiguous despite the huge sibling set.

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?

It gives clear routing context: this is a legacy-only endpoint not in the live v3 docs, expected to be removed, and the agent should 'prefer a current equivalent.' That is strong when-to-use guidance, but the alternative is never named, so an agent following the advice has no concrete substitute to select.

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