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

ghl-mcp-server-v2

by zackscriven

ghl_blog_post_list

Read-onlyIdempotent

Lists blog posts for a given blog ID, supporting pagination, status filtering, and keyword search across titles, descriptions, slugs, and categories.

Instructions

Lists all posts for a given blogId (operationId get-blog-post) — not a single-post fetch. Requires blogId + limit; paginated. Get Blog posts by Blog ID The "Get Blog posts by Blog ID" API returns the blog posts for a given blog site. Use searchTerm to search across post title, description, url slug and category name. Endpoint: GET /blogs/posts/all (Version header: v3; source: v3/blogs-v3.json) Requires a Sub-Account (location) token. OAuth scopes: blogs/posts.readonly Pagination params: limit, offset — 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": {
      "locationId": "<locationId>",
      "limit": "<limit>",
      "offset": "<offset>",
      "blogId": "<blogId>"
    },
    "name": "ghl_blog_post_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesMaximum number of records to return (0-50)
blogIdYesIdentifier of the blog site whose posts are being listed
offsetYesNumber of records to skip for pagination
statusNoFilter by publication status
locationIdYesSub-account (location) identifier whose posts are being listed
searchTermNoFree-text search across post title, description, url slug and category name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv2.1.0
    • addedInput schema / properties / blogId / description
      Added value: +"Identifier of the blog site whose posts are being listed"
    • addedInput schema / properties / blogId / example
      Added value: +"lMOzIQZne5m6zQ528sT6"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records to return (0-50)"
    • addedInput schema / properties / limit / example
      Added value: +10
    • addedInput schema / properties / locationId / description
      Added value: +"Sub-account (location) identifier whose posts are being listed"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
    • addedInput schema / properties / offset / description
      Added value: +"Number of records to skip for pagination"
    • addedInput schema / properties / offset / example
      Added value: +0
    • changedInput schema / properties / searchTerm / description
      Previous value: -"search for any post by name"New value: +"Free-text search across post title, description, url slug and category name"
    • addedInput schema / properties / searchTerm / example
      Added value: +"marketing"
    • addedInput schema / properties / status / description
      Added value: +"Filter by publication status"
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "ALL",
      -  "PUBLISHED",
      -  "SCHEDULED",
      -  "ARCHIVED",
      -  "DRAFT"
      -]New value: +[
      +  "ALL",
      +  "DRAFT",
      +  "PUBLISHED",
      +  "SCHEDULED",
      +  "SCHEDULE_FAILED",
      +  "ARCHIVED",
      +  "DELETED"
      +]
    • addedInput schema / properties / status / example
      Added value: +"PUBLISHED"
    • changedInput schema / required
      Previous value: -[
      -  "locationId",
      -  "blogId",
      -  "limit",
      -  "offset"
      -]New value: +[
      +  "locationId",
      +  "limit",
      +  "offset",
      +  "blogId"
      +]
  2. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the credit is for the extra operational facts: Sub-Account (location) token required, OAuth scope blogs/posts.readonly, endpoint GET /blogs/posts/all with a v3 version header, and that limit/offset are the paging controls for full result sets. It doesn't say what happens when limit exceeds 50 or how to detect the last page.

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 sentence is well front-loaded, but the second sentence ('Get Blog posts by Blog ID / The "Get Blog posts by Blog ID" API returns...') restates the same purpose twice and duplicates the annotation title. Endpoint/version/source metadata could be compressed into one clause.

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, paginated list with no output schema, the description supplies auth model, scope, endpoint, and paging mechanics — enough to call it correctly. It omits the shape of a returned post and any indication of default sort order or total-count availability.

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 coverage is 100%, so the baseline is 3; the description only restates the pagination role of limit/offset and the fields searchTerm covers. It also says 'Requires blogId + limit' while locationId and offset are equally required, a small inaccuracy that could mislead about the mandatory set.

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?

Opens with a specific verb+resource ('Lists all posts for a given blogId') and explicitly excludes the single-post read, which is exactly the distinction versus sibling ghl_blog_get_post_by_id. An agent can pick this tool 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 Guidelines4/5

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

The negative clause ('not a single-post fetch') steers away from the get-by-id sibling, and the searchTerm sentence explains a filtering path that belongs to this list tool rather than a search tool. It stops short of naming the alternative or stating exclusions such as 'use ghl_blog_get_post_by_id when you have a postId'.

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