HighLevel

Inspect one operationId from search_operations. Returns compact public params, requestBodyFields, one sanitized payloadExample, scopes, safety metadata, and idempotency constraints before calling execute_operation.

describe_operation

Execute one active operation from the generated GHL public operation registry after server-side scope, permission, safety, idempotency, and tenant checks. Params may be grouped as {path, query, header, body} or provided flat; the server maps known path/query/body fields and applies Authorization and Version. Location handling depends on the connection: a single-location connection injects its bound location automatically; a multi-location connection requires locationId (call list_locations first) and authorizes it before executing. Call describe_operation first when the body or params are unclear.

execute_operation

List the sub-accounts (locations) this connection can operate on, so the user can pick one. When the user names a location, pass `query` with that name instead of paginating. When many locations exist and none was named, ask the user which one rather than enumerating pages. Returns location names and ids only — never credentials. On a single-location connection this returns exactly the one bound location.

list_locations

Find an executable GHL public API operation, including operations that search for specific records by name, email, phone, or other fields. Call describe_operation for the selected operationId when hasRequestBody is true or params are unclear, then call execute_operation. Managed Agents support list/get with UI links: for execution requests, retrieve the agent and give a brief link handoff stating nothing was started. Do not promise manual execution in the UI or offer to recreate the agent’s workflow.

search_operations