Skip to main content
Glama

HighLevel Agency & Builder MCP

Find tools and workflow templates

ghl_agency_tools_search
Read-onlyIdempotent

Find tools and workflow templates by keyword or category.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ghl_agency_tools_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / category / description
      Removed value: -"Optional template category filter."
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "all",
      -  "core",
      -  "onboarding",
      -  "saas",
      -  "ai",
      -  "telephony",
      -  "commerce",
      -  "governance",
      -  "crm",
      -  "billing",
      -  "announcements"
      -]New value: +[
      +  "all",
      +  "core",
      +  "onboarding",
      +  "crm",
      +  "telephony",
      +  "governance"
      +]
    • removedInput schema / properties / query / description
      Removed value: -"Keyword to search across blueprint templates and descriptions."
    • changedInput schema / properties / query / maxLength
      Previous value: -16384New value: +512
  2. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Optional template category filter."
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "all",
      -  "core",
      -  "onboarding",
      -  "crm",
      -  "telephony",
      -  "governance"
      -]New value: +[
      +  "all",
      +  "core",
      +  "onboarding",
      +  "saas",
      +  "ai",
      +  "telephony",
      +  "commerce",
      +  "governance",
      +  "crm",
      +  "billing",
      +  "announcements"
      +]
    • addedInput schema / properties / query / description
      Added value: +"Keyword to search across blueprint templates and descriptions."
    • changedInput schema / properties / query / maxLength
      Previous value: -512New value: +16384
  3. Changed4 schema fields changed
    • removedInput schema / properties / category / description
      Removed value: -"Optional template category filter."
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "all",
      -  "core",
      -  "onboarding",
      -  "saas",
      -  "ai",
      -  "telephony",
      -  "commerce",
      -  "governance",
      -  "crm",
      -  "billing",
      -  "announcements"
      -]New value: +[
      +  "all",
      +  "core",
      +  "onboarding",
      +  "crm",
      +  "telephony",
      +  "governance"
      +]
    • removedInput schema / properties / query / description
      Removed value: -"Keyword to search across blueprint templates and descriptions."
    • changedInput schema / properties / query / maxLength
      Previous value: -16384New value: +512
  4. Changed3 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Optional template category filter.",
      +  "enum": [
      +    "all",
      +    "core",
      +    "onboarding",
      +    "saas",
      +    "ai",
      +    "telephony",
      +    "commerce",
      +    "governance",
      +    "crm",
      +    "billing",
      +    "announcements"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / pack
      Removed value: -{
      -  "description": "Optional tool pack filter.",
      -  "enum": [
      -    "all",
      -    "core",
      -    "onboarding",
      -    "saas",
      -    "ai",
      -    "telephony",
      -    "commerce",
      -    "governance",
      -    "crm",
      -    "billing",
      -    "announcements"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / properties / query / description
      Previous value: -"Keyword to search across tool names and descriptions."New value: +"Keyword to search across blueprint templates and descriptions."
  5. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds nothing further. It says nothing about result set size, pagination, or whether 'open world' means results may include items not yet available in the caller's agency.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the missing usage and parameter detail noted elsewhere.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does not. For an open-world discovery tool sitting next to an enable tool, the agent has no picture of result shape, ranking, or the search-to-enable handoff.

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 description coverage is 0%, so the description must compensate, and it does only minimally by mapping 'keyword' to query and 'category' to category. It does not clarify whether the two filters combine (AND) or whether category='all' overrides query, nor what the enum values core/onboarding/governance actually cover.

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?

States a specific verb and resource ('Find tools and workflow templates') plus the two filter axes, so the agent knows exactly what is being retrieved. It does not distinguish itself from the sibling ghl_agency_tools_enable, which reads like the complementary write side of the same object, so a reader must infer that this one is discovery-only.

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 when-to-use or when-not-to-use guidance, and no mention that this tool only locates tools/templates while ghl_agency_tools_enable is what actually enables them. The agent is left to guess whether search also installs anything.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.