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

ghl-mcp-server-v2

by zackscriven

ghl_saas_get_locations

Read-onlyIdempotent

Fetches all SaaS-activated locations for a company using pagination, requiring an agency-level token.

Instructions

REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only. page is a required query param per spec. Get SaaS Locations Fetch all SaaS-activated locations for a company with pagination Endpoint: GET /saas/saas-locations/{companyId} (Version header: v3; source: v3/saas-api-v3.json) Requires an Agency (company-level) token. OAuth scopes: saas/company.read 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>",
      "page": "<page>"
    },
    "name": "ghl_saas_get_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
companyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful context beyond them: the required token tier, the specific OAuth scope, the endpoint and API version, and that results are paginated. It stops short of describing the response envelope or page-size limits, which keeps it off a 5.

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 critical constraint is front-loaded in the first line, which is good. But the agency-token requirement is stated twice (once in the header, once mid-description), and the line 'Pagination params: page — pass them to page through full result sets' is awkward and grammatically confused for a single parameter.

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?

There is no output schema, so the description should ideally sketch the returned shape (list of locations plus pagination metadata) and say how to obtain a valid companyId. Auth, scope, and pagination are covered, and annotations cover the safety profile, leaving the return contract as the notable gap.

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 carries the full burden. It does explain that `page` is a required query param and that it drives paging through the full result set, but it says nothing specific about `companyId` beyond the endpoint path template — an agent gets no hint that this is the agency/company ID rather than a location ID.

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 and resource: 'Fetch all SaaS-activated locations for a company with pagination.' That is far more precise than the name alone and scopes the result set to SaaS-activated locations. It does not, however, distinguish itself from close siblings such as ghl_saas_get_locations_by_stripe_id or the *_deprecated variant, so an agent must infer the difference.

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 gating prerequisite (Agency/company-level token, OAuth scope saas/company.read) is stated clearly, which tells the agent when the call will succeed. But there is no explicit when-to-use guidance versus alternatives, no statement of when not to use it, and no mention of which sibling to prefer for a non-SaaS location listing.

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