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

ghl-mcp-server-v2

by zackscriven

ghl_marketplace_get_installer_details

Read-onlyIdempotent

Fetches installer details for an app using its app ID, returning company, location, user, and installation data tied to the authenticated OAuth token.

Instructions

Get Installer Details Fetches installer details for the authenticated user. This endpoint returns information about the company, location, user, and installation details associated with the current OAuth token. Endpoint: GET /marketplace/app/{appId}/installations (Version header: v3; source: v3/marketplace-v3.json) Requires an Agency or Sub-Account token. OAuth access token only — Private Integration Tokens are rejected. OAuth scopes: marketplace-installer-details.readonly

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": {
      "appId": "<appId>"
    },
    "name": "ghl_marketplace_get_installer_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesID of the app to get installer details

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/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 safety profile is covered; the description adds genuinely useful context beyond that — token type restrictions, rejected credential types, API version header, and required OAuth scope. It stops short of describing error behavior or pagination, but the auth constraints are the important addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose sentence followed by return scope, endpoint, auth requirements, and scope — each line carries distinct information. Minor redundancy from restating the title, but otherwise efficient.

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?

No output schema exists, so the description compensates by naming what the response contains (company, location, user, installation details). Combined with auth and endpoint metadata, an agent has enough to invoke it correctly; only error/edge-case behavior is unaddressed.

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% and the single appId parameter is documented in the schema with an example. The description adds no format or semantics beyond that, so the baseline 3 applies — the schema does the work.

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 (fetches) and resource (installer details) and enumerates the returned entities (company, location, user, installation details) tied to the current OAuth token. It even gives the underlying endpoint, though it does not explicitly contrast itself with related marketplace siblings such as ghl_marketplace_uninstall_application or the oauth install-location tools.

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?

Provides concrete preconditions: requires an Agency or Sub-Account token, OAuth access token only, Private Integration Tokens rejected, and the specific scope marketplace-installer-details.readonly. This effectively tells the agent when the call will succeed, but offers no explicit when-to-use-vs-alternative routing.

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