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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_locations_by_stripe_id_deprecated

Read-onlyIdempotent

Retrieves company locations filtered by Stripe customer or subscription ID using a company ID. Deprecated legacy fallback requiring an agency-level token; use GET /saas/locations instead.

Instructions

DEPRECATED per spec — superseded by GET /saas/locations. 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 locations by stripeId with companyId Get locations by stripeCustomerId or stripeSubscriptionId with companyId Endpoint: GET /saas-api/public-api/locations (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": {
      "companyId": "<companyId>"
    },
    "name": "ghl_saas_get_locations_by_stripe_id_deprecated"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesCompany ID to filter locations
customerIdNoStripe customer ID to find locations for
subscriptionIdNoStripe subscription ID to find locations 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?

Annotations already cover read-only/idempotent/non-destructive, but the description adds material context beyond them: an Agency (company-level) token is required, the 2021-04-15 Version header is needed, and removal is expected. That is exactly the extra behavioral detail an agent needs.

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?

Deprecation is appropriately front-loaded, but it is repeated three times in near-identical bracketed notes, plus a duplicate 'requires agency token' line. The redundancy dilutes rather than informs.

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 read-only legacy lookup with no output schema, the description covers auth scope, version header, deprecation status, and lookup keys. Little an agent needs is missing, aside from the exact successor tool name.

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%, so all three parameters are documented in the schema. The description restates the two lookup modes but adds no format or selection logic beyond what the schema provides, so 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 specific verb+resource plus the alternative lookup keys (stripeId/stripeCustomerId/stripeSubscriptionId) and the underlying endpoint. It does not name the sibling ghl_saas_get_locations_by_stripe_id, but the deprecation routing is clear.

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 it is deprecated, superseded by GET /saas/locations, and only served under a legacy Version header — a strong when-not-to-use signal. It stops short of naming the exact replacement tool to call.

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