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

ghl-mcp-server-v2

by zackscriven

ghl_social_category_list

Read-onlyIdempotent

Retrieve social media posting categories by location ID, with optional search and pagination to page through results.

Instructions

Get categories by location ID Retrieve all categories for a specific location with optional search and pagination Endpoint: GET /social-media-posting/{locationId}/categories (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/category.readonly Pagination params: limit, skip — 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>"
    },
    "name": "ghl_social_category_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoSkip
limitNoLimit
locationIdYesLocation Id
searchTextNoSearch text string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / limit / example
      Added value: +"10"
    • addedInput schema / properties / locationId / example
      Added value: +"ve9EPM428h8vShlRW1KT"
    • addedInput schema / properties / searchText / example
      Added value: +"test"
    • addedInput schema / properties / skip / example
      Added value: +"0"
  2. First observedv2.0.0

TDQS

A3.8/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 useful operational context beyond them: the Sub-Account token requirement, the OAuth scope (socialplanner/category.readonly), and the API version header. It does not mention rate limits or whether results are truncated beyond the paging hint.

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 purpose, then endpoint, auth, and pagination. Slightly redundant because 'Get categories by location ID' restates the title, and the source-file reference is low value for an agent, but nothing is padding.

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?

No output schema, but the description makes clear this returns a collection of categories scoped to a location and that paging is needed for large sets. Adequate for a simple read/list tool; a note on what a category object contains would complete it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but schema descriptions are bare ('Skip', 'Limit'). The description compensates by explaining that limit/skip are pagination controls for paging through full result sets and flags searchText as an optional search, which the schema's 'Search text string' leaves ambiguous about scope.

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+resource ('Retrieve all categories for a specific location') and the scope (per-location). However it never distinguishes itself from the close sibling ghl_social_category_get, so an agent must infer 'list' vs 'get' from the name alone.

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 only implied by 'Retrieve all' and the pagination note. There is no explicit 'use this to enumerate categories, use ghl_social_category_get to fetch one by ID' guidance, despite that sibling being present.

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