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

ghl-mcp-server-v2

by zackscriven

ghl_saas_update_saas_subscription_deprecated

Idempotent

Updates an existing SaaS subscription plan or pricing for a specific location and customer using an agency-level token. Deprecated: use the documented replacement endpoint instead.

Instructions

DEPRECATED per spec — superseded by PUT /saas/update-saas-subscription/{locationId}. REQUIRES AN AGENCY-LEVEL (Company) TOKEN. NOTE: the generated name for this op was misleading ('generate_payment_link'); corrected to reflect what the op actually does (updates an existing SaaS subscription plan/pricing), matching its summary 'Update SaaS subscription'. [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.] Update SaaS subscription Update SaaS subscription for given locationId and customerId Endpoint: PUT /saas-api/public-api/update-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>",
      "body": "<body>"
    },
    "name": "ghl_saas_update_saas_subscription_deprecated"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation ID to update subscription for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: an agency/company-level token is required, the operation is served only under the legacy Version header (2021-04-15), and removal is expected. Annotations already cover the mutation/idempotency profile, so this auth and lifecycle disclosure is the 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.

Conciseness3/5

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

The deprecation warning is correctly front-loaded, but it is then repeated three times in near-identical bracketed notices, plus a redundant endpoint line and a repeated token-requirement sentence. The signal is right; the duplication costs it.

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?

With two required params, a nested body, annotations present, and no output schema, the agent needs auth scope, lifecycle risk, and endpoint identity — all supplied. Only the exact replacement tool name is missing.

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 locationId, subscriptionId, customerId, and companyId are already documented in the schema. The description only adds that locationId is a path parameter and that the body is carried verbatim from the OpenAPI spec — no semantic enrichment. Baseline 3.

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 ('updates an existing SaaS subscription plan/pricing') and clarifies the misleading generated name 'generate_payment_link'. It names the superseding endpoint PUT /saas/update-saas-subscription/{locationId}, which effectively routes an agent away from the non-deprecated sibling ghl_saas_update_saas_subscription, though it never names that tool directly.

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, superseded, and a legacy fallback likely to be removed, with repeated instructions to prefer a current equivalent. The only weakness is the hedge 'prefer the documented replacement if one exists' rather than naming the sibling tool outright.

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