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

ghl-mcp-server-v2

by zackscriven

ghl_social_category_get

Read-onlyIdempotent

Retrieve a specific social media posting category by its ID and location ID. Use it to fetch category details for a GoHighLevel sub-account.

Instructions

Get category by ID Retrieve a specific category by its ID Endpoint: GET /social-media-posting/{locationId}/categories/{id} (Version header: v3; source: v3/social-planner-v3.json) Requires a Sub-Account (location) token. OAuth scopes: socialplanner/category.readonly

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": {
      "id": "<id>",
      "locationId": "<locationId>"
    },
    "name": "ghl_social_category_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCategory Id
locationIdYesLocation Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / id / example
      Added value: +"6284c43d519161e96cc09c13"
    • addedInput schema / properties / locationId / example
      Added value: +"6284c43d519161e96cc09c13"
  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=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond that: the concrete endpoint and path shape, required API version header, required token class, and OAuth scope. It says nothing about not-found behavior, which is the remaining gap.

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?

Purpose is front-loaded, but the first two lines are a redundant restatement of one another, and the internal source path '(source: v3/social-planner-v3.json)' is noise for an agent choosing a tool. Roughly half the text earns its place.

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 simple two-parameter read tool with full annotation coverage, the description supplies what the structured fields cannot: auth requirements, scope, endpoint, and API version. With no output schema, a one-line note on the response shape would close the remaining 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 'id' and 'locationId' are already documented by the schema, and the baseline is 3. The endpoint template implicitly confirms both are path parameters, but the description adds no format, source-of-value, or ID-lookup guidance beyond that.

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 ('Retrieve a specific category by its ID'), so the agent knows exactly what it returns. However, the first two lines say the same thing twice and nothing distinguishes it from sibling readers like ghl_social_category_list or ghl_social_fetch_available_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 establishes prerequisites (Sub-Account/location token, socialplanner/category.readonly scope) and implies the tool is for fetching one known category ID. It never says when to prefer category_list or fetch_available_categories instead, so the selection guidance is only implied.

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