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

ghl-mcp-server-v2

by zackscriven

ghl_kb_crawler_list_urls

Read-onlyIdempotent

Lists discovered and trained website pages for a knowledge base with pagination and an optional URL filter, so you can inspect crawled pages the AI can use.

Instructions

Get all trained page links by knowledge base Lists discovered and trained website pages for a knowledge base, with pagination and optional URL filter. WHEN TO USE: use this when you need to inspect crawled pages; use discoverWebsite to find new pages; use deleteTrainedUrlsForKnowledgeBase to remove pages the AI should stop using. RETURNS: a paginated list of crawled URLs with status, title, and identifiers. Endpoint: GET /knowledge-bases/crawler (Version header: v3; source: v3/knowledge-base-v3.json) Requires a Sub-Account (location) token. OAuth scopes: knowledge-bases.readonly Pagination params: page, pageLength — pass them to page through full result sets.

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>",
      "locationId": "<locationId>"
    },
    "name": "ghl_kb_crawler_list_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
queryNoquery to filter on url links
locationIdYeslocation ID as string
pageLengthNoRecords per page
knowledgeBaseIdYesknowledge base ID as string

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds context annotations cannot: Sub-Account (location) token requirement, knowledge-bases.readonly OAuth scope, endpoint/version, and pagination behavior for full result sets. It stops short of noting rate limits or ordering of results.

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?

Front-loaded and well-structured into WHEN TO USE / RETURNS / endpoint / pagination sections. The opening line 'Get all trained page links by knowledge base' duplicates the title and the following sentence, costing one point of economy.

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 paginated list tool with no output schema, the description covers scope, required identifiers, auth, and the shape of returned records (status, title, identifiers). Filtering semantics of query could be spelled out more precisely, but an agent has enough to call it correctly.

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%, so page, pageLength, query, locationId and knowledgeBaseId are already documented. The description only adds the operational hint that page/pageLength should be passed to page through full result sets and that query is a URL filter — marginal value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('Lists discovered and trained website pages for a knowledge base') and distinguishes this read/list operation from the sibling mutators it names (discoverWebsite, deleteTrainedUrlsForKnowledgeBase). An agent can tell exactly what this returns without opening the schema.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE block gives the triggering condition ('inspect crawled pages') and names two alternatives with their distinct purposes (discover for new pages, delete to remove pages). Nothing is left to inference.

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