Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-ghl

by AIWerk

users_search_users

Read-onlyIdempotent

Search users in GoHighLevel by name, email, phone, role, type, or ID. Apply filters like skip, limit, and sorting to retrieve targeted user records.

Instructions

Search Users

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 result
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 result
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 Defaults to GHL_LOCATION_ID when omitted.
sortDirectionNoThe direction in which the results need to be sorted
enabled2waySyncNo
Behavior2/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint), but the description adds no behavioral context beyond the bare action. It does not disclose pagination behavior, filtering options, or other runtime aspects that would help the agent anticipate results.

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?

The description is extremely short ('Search Users'), which is technically concise but under-specified. It does not front-load any useful context or nuance that would help the agent understand the tool's behavior or intended use, falling below the threshold of appropriate conciseness.

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

Completeness2/5

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

Despite having 11 parameters and no output schema, the description provides no overview of how the search works, what filters are available, or what the result set looks like. The schema documents individual parameters but not the overall purpose, leaving a significant gap for the agent to infer.

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 91%, so most parameters are documented in the schema itself. The description adds no additional meaning to the parameters; it simply repeats 'Search Users'. Given the high schema coverage, a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb and resource ('Search Users') but is vague and does not differentiate from sibling tools like users_filter_users_by_email or users_get_user. It lacks specificity about what kind of search (e.g., general, full-text) or how it differs from more targeted user lookups.

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 such as users_filter_users_by_email or users_get_user. The description gives no context for when to choose this over a more specific lookup, leaving the agent to infer usage from the schema alone.

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/AIWerk/mcp-server-ghl'

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