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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_location_subscription_deprecated

Read-onlyIdempotent

Fetch subscription details for a specific location using company and location IDs; requires an agency-level token. Deprecated legacy fallback; use the documented replacement where available.

Instructions

DEPRECATED per spec — superseded by GET /saas/get-saas-subscription/{locationId}. REQUIRES AN AGENCY-LEVEL (Company) TOKEN. [DEPRECATED per official docs — prefer the documented replacement if one exists.] [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 Location Subscription Details Fetch subscription details for a specific location from location metadata Endpoint: GET /saas-api/public-api/get-saas-subscription/{locationId} (Version header: 2021-04-15; source: saas-api.json) Requires an Agency (company-level) token.

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>",
      "companyId": "<companyId>"
    },
    "name": "ghl_saas_get_location_subscription_deprecated"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesCompany ID to filter subscription details
locationIdYesLocation ID to get subscription details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, but the description adds real behavioral context: it requires an agency-level rather than location-level token, is served only under a legacy Version header (2021-04-15), and is expected to be removed. That auth and lifecycle information is not derivable from the schema or annotations.

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

Conciseness2/5

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

The deprecation warning is stated three separate times in three bracketed blocks plus a lead sentence, which is redundant padding around a short core message. The lead sentence is front-loaded and useful, but the repetition costs space without adding information.

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 deprecated two-parameter read endpoint with no output schema, the description supplies the essentials: what it returns, where it lives, the auth level required, and the removal risk. The only gap is the absence of the replacement tool's actual name in this tool set.

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 parameters are documented in the schema. The description only echoes locationId inside the endpoint template and says nothing additional about companyId or how the two identifiers interact, so 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?

States a specific verb and resource ('Fetch subscription details for a specific location') and gives the underlying endpoint. The identification is clear, but it never names the sibling tool that replaces it (ghl_saas_get_location_subscription), naming only a REST path, so the agent must infer the mapping.

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?

Explicitly says the tool is deprecated, that a documented replacement exists, and that it should be avoided in favor of a current equivalent. It also states the prerequisite: an Agency (company-level) token. What's missing is the concrete tool name to switch to.

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