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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_locations_deprecated

Read-onlyIdempotent

Fetch all SaaS-activated locations for a company with pagination using an agency-level token; deprecated fallback endpoint, prefer the documented replacement.

Instructions

DEPRECATED per spec — superseded by GET /saas/saas-locations/{companyId}. 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 SaaS Locations Fetch all SaaS-activated locations for a company with pagination Endpoint: GET /saas-api/public-api/saas-locations/{companyId} (Version header: 2021-04-15; source: saas-api.json) Requires an Agency (company-level) token. Pagination params: page — pass them to page through full result sets.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination
companyIdYesCompany ID to get SaaS locations 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 declare readOnly/idempotent/non-destructive, so the description's added value is real: agency-level token requirement, the legacy Version header (2021-04-15), the fact it is no longer in live v3 docs (checked 2026-10-28), and pending removal. It does not describe the default page size or response shape, which keeps it below 5.

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?

Three overlapping bracketed deprecation notices say substantially the same thing, and the agency-token requirement appears twice (CAPS banner and again as a sentence). The useful facts are front-loaded, but roughly a third of the text is redundant.

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 read-only list endpoint with full schema coverage and no output schema, the description covers auth level, endpoint/version, pagination, and lifecycle risk — enough to call it correctly. Only the semantics of 'SaaS-activated' and the return shape are left implicit.

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 both parameters are already documented in the schema. The note 'Pagination params: page — pass them to page through full result sets' restates the schema without adding paging semantics (default size, max page, termination). 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+resource: 'Fetch all SaaS-activated locations for a company with pagination,' and the concrete endpoint path. It signals supersession ('superseded by GET /saas/saas-locations/{companyId}') but references an HTTP route rather than the sibling tool ghl_saas_get_locations, so the agent must infer the sibling mapping itself.

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?

Gives a clear 'prefer the replacement if one exists' instruction and an explicit prerequisite ('REQUIRES AN AGENCY-LEVEL (Company) TOKEN'), which is genuine when-to-use guidance. It falls short of 5 because the alternative is only named as a URL, not as a tool the agent can actually 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