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

ghl-mcp-server-v2

by zackscriven

ghl_blog_get_all_authors_by_location

Read-onlyIdempotent

Fetch blog authors for a given location ID, with limit/offset pagination and optional search across author name and description.

Instructions

Get all blog authors The "Get all blog authors" API returns the blog authors for a given location ID. Endpoint: GET /blogs/authors (Version header: v3; source: v3/blogs-v3.json) Requires a Sub-Account (location) token. OAuth scopes: blogs/author.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>"
    },
    "name": "ghl_blog_get_all_authors_by_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesMaximum number of authors to return (0-50)
offsetYesNumber of authors to skip before returning results
locationIdYesSub-account (location) identifier the author belongs to
searchTermNoFree-text search across author name and description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.1.0
    • changedInput schema / properties / limit / description
      Previous value: -"Number of authors to show in the listing"New value: +"Maximum number of authors to return (0-50)"
    • addedInput schema / properties / limit / example
      Added value: +10
    • changedInput schema / properties / locationId / description
      Previous value: -"Location Id"New value: +"Sub-account (location) identifier the author belongs to"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
    • changedInput schema / properties / offset / description
      Previous value: -"Number of authors to skip in listing"New value: +"Number of authors to skip before returning results"
    • addedInput schema / properties / offset / example
      Added value: +0
    • addedInput schema / properties / searchTerm
      Added value: +{
      +  "description": "Free-text search across author name and description",
      +  "example": "jane",
      +  "type": "string"
      +}
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely non-obvious context: it requires a Sub-Account (location) token and the blogs/author.readonly OAuth scope. That auth prerequisite is the kind of information an agent cannot infer from annotations or schema.

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 with the purpose in the first sentence, followed by endpoint, auth and pagination details in tight lines. Minor redundancy between the title and the quoted API summary, but no filler.

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 full schema coverage and no output schema, the definition supplies endpoint version, auth token type, OAuth scope, and pagination mechanics. Only the response shape (e.g. whether the authors array is wrapped) is unaddressed, which is a minor gap.

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 limit, offset, locationId and searchTerm are already documented including the 0-50 cap. The description's note that limit/offset should be passed to page through full result sets adds slight usage value but no semantics beyond the schema; baseline 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 all blog authors') and scopes it to a location ID. Sibling tools like ghl_blog_get_all_categories_by_location and ghl_blog_post_list are implicitly distinguished by resource (authors vs categories vs posts), though no sibling is named explicitly.

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 is implied: call it when you need the authors for a given location, paging with limit/offset. There is no explicit when-not guidance and no routing to an alternative tool (e.g. category listing or post listing) when the agent is unsure which blog resource to fetch.

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