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

ghl-mcp-server-v2

by zackscriven

ghl_social_fetch_queues

Retrieve paginated category queues for a specific location, excluding deleted queues, to review or manage social media posting categories.

Instructions

Fetch category queues for a location Retrieves a paginated list of all category queues for a given location, excluding any that have been marked as deleted. Endpoint: POST /social-media-posting/category/queues/list (Version header: v3; source: v3/social-planner-v3.json) 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": {
      "body": "<body>"
    },
    "name": "ghl_social_fetch_queues"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"FetchCategoryQueuesDTO"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Adds real context beyond the annotations: the OAuth scope required (socialplanner/category.readonly), the endpoint version header, and the filtering behavior (deleted queues excluded). However the read-only framing of 'retrieves a paginated list' sits awkwardly against the annotation readOnlyHint=false, and no pagination defaults or result shape are given for a tool with no output 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-loads the one-line purpose, then a clarifying sentence, then terse endpoint/scope metadata. The endpoint path and spec-source parenthetical are plumbing rather than guidance, but they are compact and do not bury the useful content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should convey something about the returned collection; it says 'paginated list' and notes deleted items are omitted, but gives no field shape, default page size, or total-count behavior. Enough to call it correctly, not enough to predict the response.

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% and each nested body field (skip, limit, locationId) already carries its own description and example, so the definition does not need to re-document them. The description only reinforces location scoping and pagination, matching the baseline for fully documented schemas.

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 ('Fetch category queues'), plus scope ('for a location') and the exclusion of deleted entries. It does not explicitly name how it differs from close siblings such as ghl_social_fetch_queue_items or ghl_social_fetch_available_categories, leaving that separation to the reader.

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: the location scoping and 'excluding deleted' note suggest a read of configured queues, but there is no statement of when to choose this over sibling queue/category tools or what preconditions apply. Adequate but with a clear routing gap in a very crowded social-planning namespace.

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