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

ghl-mcp-server-v2

by zackscriven

ghl_saas_update_saas_subscription

Idempotent

Updates an existing SaaS subscription's plan or pricing for a location using agency-level access. Use it to change subscription details for a customer by locationId, customerId, and subscriptionId.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. Updates an existing SaaS subscription's plan/pricing for the location. NOTE: the generated name for this op was misleading ('generate_payment_link'); corrected to reflect what the op actually does, matching its summary 'Update SaaS subscription'. Update SaaS subscription Update SaaS subscription for given locationId and customerId Endpoint: PUT /saas/update-saas-subscription/{locationId} (Version header: v3; source: v3/saas-api-v3.json) Requires an Agency (company-level) token. OAuth scopes: saas/company.write

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"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"UpdateSubscriptionDto"
  2. 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 declare this is non-read-only, non-destructive, idempotent, and open-world. The description adds meaningful behavioral context beyond those annotations, including the Agency token requirement, OAuth scope, endpoint path, version header, and source spec. It does not describe the response or side effects in detail, but it does not contradict the annotations.

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 core purpose is front-loaded, but the description is repetitive and includes a meta note about the generated name that does not help an agent select or invoke the tool. The repeated 'Update SaaS subscription' phrasing and endpoint/version metadata make it longer than necessary.

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-parameter update operation with annotations and a nested body schema, the description provides enough auth, scope, endpoint, and version context to call it correctly. It does not describe the response, but no output schema exists and the description does not need to compensate for one.

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 50%, and the nested body properties are already described in the schema. The description adds that locationId and customerId identify the subscription target, but it does not explain the full required body structure or the role of subscriptionId and companyId beyond what the schema provides.

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?

The description states a specific verb and resource: updating an existing SaaS subscription for a location. It also identifies the endpoint and version, which helps distinguish the current operation from the deprecated sibling, but it does not explicitly name that sibling or fully clarify how the operation differs from it.

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?

The description establishes that an agency-level token and saas/company.write scope are required, which is useful usage context. However, it does not say when to use this operation versus alternatives such as the deprecated SaaS subscription update tool, leaving routing guidance implied.

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