Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven

ghl_user_search

Read-onlyIdempotent

Search users in a GoHighLevel account by name, email, phone, or filter by role, type, and more. Retrieve paginated results with optional sorting.

Instructions

Search Users Endpoint: GET /users/search (Version header: v3; source: v3/users-v3.json) OAuth scopes: users.readonly Pagination params: skip, limit — pass them to page through full result sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoList of User IDs to be filtered in the search
roleNoRole of the users to be filtered in the search
skipNoNo of results to be skipped before returning the result0
sortNoThe field on which sort is applied in which the results need to be sorted. Default is based on the first and last name
typeNoType of the users to be filtered in the search
limitNoNo of results to be limited before returning the result25
queryNoThe search term for the user is matched based on the user full name, email or phone
companyIdYesCompany ID in which the search needs to be performed
locationIdNoLocation ID in which the search needs to be performed
sortDirectionNoThe direction in which the results need to be sorted
enabled2waySyncNoFilter users by whether 2-way sync is enabled
Behavior3/5

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

Annotations already declare read-only and non-destructive nature. Description adds that it uses GET, OAuth scopes, and pagination. Does not mention response structure or behavior beyond pagination, which is useful but not fully comprehensive.

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?

Description is short and to the point, with no wasted words. Includes endpoint, scopes, and key pagination note. Could be slightly more streamlined by omitting technical source details, but overall efficient.

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?

Given high schema coverage and annotations, the description is adequate but missing details about search behavior (e.g., fuzzy matching, OR conditions) and response structure. Sufficient for basic use but could be improved.

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 detailed descriptions for each parameter. Description only explicitly mentions skip and limit for pagination, adding minimal value 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?

Description clearly states 'Search Users' and provides endpoint, making the tool's purpose clear. However, it does not explicitly differentiate from sibling tools like ghl_user_filter_by_email, though the name implies a broader search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., ghl_user_get or ghl_user_filter_by_email). Only mentions pagination parameters, not usage context or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zackscriven/ghl-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server