Skip to main content
Glama
zackscriven

ghl-mcp-server-v2

by zackscriven
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ghl_blog_site_list

Read-onlyIdempotent

List blog sites for a GoHighLevel sub-account by location ID, with pagination and text search to find relevant blogs.

Instructions

Get Blogs by Location ID The "Get Blogs by Location ID" API allows you get blogs using Location ID. Endpoint: GET /blogs/site/all (Version header: v3; source: v3/blogs-v3.json) Requires a Sub-Account (location) token. OAuth scopes: blogs/list.readonly Pagination params: skip, limit — pass them to page through full result sets.

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of records to skip for pagination
limitNoMaximum number of records to return
locationIdYesSub-account (location) identifier whose blog sites are being listed
searchTermNoFree-text search across blog site name and description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv2.1.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records to return"
    • addedInput schema / properties / limit / example
      Added value: +10
    • addedInput schema / properties / locationId / description
      Added value: +"Sub-account (location) identifier whose blog sites are being listed"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
    • changedInput schema / properties / searchTerm / description
      Previous value: -"search for any post by name"New value: +"Free-text search across blog site name and description"
    • addedInput schema / properties / searchTerm / example
      Added value: +"marketing"
    • addedInput schema / properties / skip / description
      Added value: +"Number of records to skip for pagination"
    • addedInput schema / properties / skip / example
      Added value: +0
    • changedInput schema / required
      Previous value: -[
-  "locationId",
-  "skip",
-  "limit"
-]New value: +[
+  "locationId"
+]
  2. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description still adds genuine context beyond that: the required Sub-Account token type, the OAuth scope, and the pagination behavior for full result sets.

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?

The first two lines are redundant — the title restated, then a near-tautological sentence repeating 'get blogs using Location ID' — before useful content (endpoint, auth, scope, pagination) arrives. Operationally valuable material is present but not front-loaded.

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 read-only list endpoint with a full schema and no output schema, the definition covers auth, scope, endpoint, and pagination, which is enough to invoke correctly. Only the return shape and the distinction from other blog listing tools are left unstated.

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 all four parameters (including searchTerm and locationId) are already documented in the schema. The description only reinforces the pagination params and adds no syntax or semantics the schema lacks, so the baseline of 3 applies.

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 (get blogs, by location ID) and names the required identifier. It does not differentiate from nearby blog siblings such as ghl_blog_post_list, ghl_blog_get_all_authors_by_location, or ghl_blog_get_all_categories_by_location, so an agent must infer that this returns blog *sites* rather than posts, authors, or categories.

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?

The description gives operational context (needs a Sub-Account token, blogs/list.readonly scope, use skip/limit to page through full result sets), which implies when it is callable. But there is no explicit guidance on when to choose this over the sibling blog listing tools, and no stated exclusions.

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