Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_location_task_search

Search tasks within a GoHighLevel location by keyword, completion status, contact, assignee, or business ID, with pagination for retrieving matching results.

Instructions

Task Search Filter Task Search Endpoint: POST /locations/{locationId}/tasks/search (Version header: v3; source: v3/locations-v3.json) OAuth scopes: locations/tasks.readonly

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locationId": "<locationId>",
      "body": "<body>"
    },
    "name": "ghl_location_task_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"TaskSearchParamsDto"
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior3/5

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

The endpoint path, API version and required OAuth scope (locations/tasks.readonly) are genuinely useful extras that the annotations do not convey, telling the agent about auth requirements. However, pagination behavior (skip/limit defaults), result ordering, and whether the search is full-text or prefix matching are not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the repeated 'Task Search' labels plus an internal source path (v3/locations-v3.json) are filler. The one high-value line (OAuth scope) is buried last.

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

Completeness4/5

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

For a two-parameter search tool with a fully documented nested body schema and no output schema, the description supplies the endpoint and auth scope, which is most of what an agent needs to call it. It falls short only on result/pagination expectations, which is a minor gap at this complexity.

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 100% with per-field descriptions and examples for query, completed, contactId, assignedTo, businessId, skip and limit, so the schema already carries parameter meaning. The description adds nothing about how those filters combine (AND semantics) or how 'query' matches, so baseline 3 applies.

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?

"Task Search Filter / Task Search" states a verb and resource, so the general function (search tasks) is inferable. But it says nothing about scope — location-wide vs contact vs project — and does not distinguish itself from siblings like ghl_contact_get_all_tasks or ghl_project_search_tasks.

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 search versus the contact-level or project-level task listing siblings, and no prerequisites beyond the OAuth scope mention. The agent must infer applicability entirely from the name.

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

Deploy Server

Other Tools