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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_locations_by_stripe_id

Read-onlyIdempotent

Retrieve agency locations by Stripe customer or subscription ID with a company ID, requiring an agency-level token and both customer and subscription query parameters.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. customerId and subscriptionId are both required query params per spec (unlike the deprecated /saas-api twin, where they're optional). Get locations by stripeId with companyId Get locations by stripeCustomerId or stripeSubscriptionId with companyId Endpoint: GET /saas/locations (Version header: v3; source: v3/saas-api-v3.json) Requires an Agency (company-level) token. OAuth scopes: saas/company.read

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": {
      "customerId": "<customerId>",
      "subscriptionId": "<subscriptionId>"
    },
    "name": "ghl_saas_get_locations_by_stripe_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYes
subscriptionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • removedInput schema / properties / companyId
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "customerId",
      -  "subscriptionId",
      -  "companyId"
      -]New value: +[
      +  "customerId",
      +  "subscriptionId"
      +]
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely useful context beyond them: an Agency-level token is mandatory, the required OAuth scope is saas/company.read, and the v3 version header must be sent. It does not describe the response shape or pagination, but the auth and versioning disclosure is substantial.

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 agency-token requirement is stated three separate times ('REQUIRES AN AGENCY-LEVEL (Company) TOKEN', 'spec security is Agency-Access-Only', 'Requires an Agency (company-level) token'), and the two 'Get locations by ...' lines restate the same operation. The content is useful but poorly front-loaded and repetitive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-param read tool with annotations but no output schema and 0% schema descriptions, the description covers auth, scope, required parameters and the version header. What is missing is how the two identifiers interact (AND vs OR) and any hint of what the returned locations contain, which matters since no output schema exists.

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 0%, so the description must carry parameter meaning, and it only partially does: it maps customerId to stripeCustomerId and subscriptionId to stripeSubscriptionId and asserts both are required. However, the prose 'by stripeCustomerId or stripeSubscriptionId' suggests an either/or lookup while the schema requires both, leaving the actual semantics of combining them unexplained.

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 gives a specific verb+resource: retrieve locations matched by Stripe customer or subscription ID, scoped to a company. It also differentiates itself from the deprecated /saas-api twin and implicitly from ghl_saas_get_locations by framing the lookup around Stripe identifiers. The duplicated headline lines muddy it slightly but the purpose is unambiguous.

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 only implied: the note that customerId/subscriptionId are required 'unlike the deprecated /saas-api twin' signals this is the version to prefer. There is no explicit statement of when to choose this over ghl_saas_get_locations or ghl_saas_get_locations_by_stripe_id_deprecated, so the agent must infer from the name and the deprecation remark.

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