GoHighLevel MCP

ghl_get_crawler_status

Check website crawling operation status using operation and knowledge base IDs. Get aggregate counts and per-URL details to monitor pending, successful, and failed crawls.

Instructions

Check the status of a website crawling operation. Returns aggregate status counts (Pending, Successful, Failed, etc.) and per-URL details.

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": {
      "knowledgeBaseId": "<knowledgeBaseId>",
      "operationId": "<operationId>"
    },
    "name": "ghl_get_crawler_status"
  }
}

Input Schema

Name	Required	Description	Default
`operationId`	Yes	Operation ID returned from ghl_discover_website — identifies the crawl job
`knowledgeBaseId`	Yes	Knowledge base ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the return format (aggregate status counts and per-URL details), which is useful. However, it does not explicitly state that this is a read-only operation, nor does it mention authentication, rate limits, pagination, or error behavior.

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

Conciseness5/5

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

The description is two concise sentences, front-loaded with the main purpose, and every word adds value. There is no redundancy or filler.

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

Completeness3/5

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

For a simple status-check tool with no output schema, the description adequately covers the return values at a high level. However, it lacks lifecycle context such as when a crawl is complete, typical wait times, or how to interpret specific statuses, which would be useful for an agent.

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 both parameters fully described, including the fact that operationId comes from ghl_discover_website. The description adds no extra parameter context, so a baseline score of 3 is appropriate.

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?

The description clearly states the tool's purpose: 'Check the status of a website crawling operation' with a specific verb and resource, and mentions the return values. However, it does not explicitly differentiate from sibling tools like ghl_list_crawler_urls, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than explicit. The description suggests the tool is used after starting a crawl, but it does not mention when to use it versus alternatives or provide any exclusions. No reference to ghl_discover_website or other lifecycle steps.

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

Deploy Server