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

ghl-mcp-server-v2

by zackscriven

ghl_location_get_conversation_channel

Read-onlyIdempotent

Retrieves the conversation channel providers configured for a location, filtered by type (SMS or Email).

Instructions

Get Conversation Channel Get the conversation channel providers configured for a location by type (SMS or Email) Endpoint: GET /locations/{locationId}/conversationChannels/{type} (Version header: v3; source: v3/locations-v3.json) Requires a Sub-Account (location) token. OAuth scopes: locations.readonly

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>",
      "type": "<type>"
    },
    "name": "ghl_location_get_conversation_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesChannel type to retrieve providers for
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds material context beyond them: it requires a Sub-Account (location) token and needs the locations.readonly OAuth scope, plus the endpoint and API version. That kind of auth and endpoint detail is exactly what prevents failed calls.

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?

Front-loaded with the action and the constraint, followed by endpoint metadata and auth requirements. Slightly metadata-heavy for a two-parameter read, but every line (scope, token type, version) is actionable rather than filler.

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?

Covers purpose, auth model, scope, and endpoint for a simple read-only two-parameter call. No output schema exists, so a note on the returned provider structure would have been a plus, but it is a minor gap for a low-complexity lookup.

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 coverage is 100% with both parameters documented and the type enum spelled out, so the schema carries the parameter burden. The description's 'by type (SMS or Email)' merely restates the enum values already present in the schema, adding no new syntax or format guidance.

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 (get) and resource (conversation channel providers) plus the scope of the lookup (per location, by channel type). It is unambiguous on its own, though it does not name any sibling to distinguish against — largely unnecessary here since no other conversation-channel tool exists in the sibling list.

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

Usage Guidelines3/5

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

Usage is implied by 'get the conversation channel providers configured for a location by type (SMS or Email)', which tells the agent the retrieval context. However there is no explicit when-to-use guidance, no mention of alternatives, and no statement of when this tool is not appropriate.

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