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

ghl-mcp-server-v2

by zackscriven

ghl_user_get

Read-onlyIdempotent

Retrieve a GoHighLevel user by userId to view user details; requires an agency or sub-account token with users.readonly scope.

Instructions

Get User Endpoint: GET /users/{userId} (Version header: v3; source: v3/users-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: users.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": {
      "userId": "<userId>"
    },
    "name": "ghl_user_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesUser Id

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 declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds genuine value beyond that: the required token type and the users.readonly OAuth scope, which govern whether a call will be authorized at all.

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?

Four short lines, front-loaded with the operation and then the endpoint and auth facts. The source-file reference (v3/users-v3.json) is internal provenance that does little for an agent, a minor bit of waste.

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

Completeness5/5

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

For a single-ID read tool with one fully documented parameter, read-only annotations, and no output schema, the description covers what an agent needs to know: the exact endpoint, the token tier, and the scope. Nothing essential to calling it correctly is missing.

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% with a single required userId, so the schema already carries the parameter documentation. The description only implies the ID is a path segment via the endpoint template and adds no format, sourcing, or validation detail beyond the schema.

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 (Get User) and pins it to GET /users/{userId}, which implicitly distinguishes it from the list/search siblings like ghl_user_search and ghl_user_get_by_location. It never explicitly names an alternative, so sibling differentiation is inferred rather than stated.

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 prerequisite 'Requires an Agency or Sub-Account token' is useful context for when this tool will succeed. However, there is no guidance on when to pick this over ghl_user_get_by_location, ghl_user_search, or ghl_user_filter_by_email, so the routing decision is left to inference.

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