The 5 Unified Tools

Instead of listing hundreds of operations as individual tools, the server exposes 5 unified tools. The assistant uses these to discover and run everything else.

Tool	What it does
search	Find customer or business records by name, email, phone, tag, or similar criteria
fetch	Retrieve the full details of one or more records returned by search
search_operations	Discover available operations by intent (list, create, update, delete, etc.)
describe_operation	Inspect an operation's input schema before running it
execute_operation	Run one operation, subject to your scopes and built-in safety checks

Usage Pattern

Always follow this order:

1. search_operations — discover what's available for your intent
2. describe_operation — inspect the input schema
3. execute_operation — run it

Never guess the input schema. Always describe_operation first.

Example: Tag a Contact and Create an Opportunity

Natural language prompt:

"Find the contact with email jane@example.com, add the tag 'vip-2026', and create a new opportunity in the 'Sales Pipeline' for them worth $5,000."

Behind the scenes:

1. search finds Jane's contact record
2. search_operations discovers the "add tags" and "create opportunity" operations
3. describe_operation inspects the inputs each operation expects
4. execute_operation adds the tag and creates the opportunity

Result: a single natural-language confirmation.

Frankie / Frontend Usage

When building GHL-connected UIs on this box, these tools are available via the leadconnector MCP (already connected in Claude Code):

search_operations("contacts") → describe_operation("contacts.create") → execute_operation(...)

Use search_operations to explore what's available before writing any UI integration code.