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

ghl-mcp-server-v2

by zackscriven

ghl_social_fetch_queue_items

Fetch paginated social media queue items for a location, including live or edit-session drafts, with options to filter errors or center results around a specific item.

Instructions

Fetch items from a queue Returns paginated queue items. Pass sessionId to get draft items from an edit session instead of live items. Endpoint: POST /social-media-posting/category/queues/{queueId}/items (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": {
      "queueId": "<queueId>",
      "body": "<body>"
    },
    "name": "ghl_social_fetch_queue_items"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"FetchQueueItemsDTO"
    • addedInput schema / properties / queueId / description
      Added value: +"Category queue ID"
    • addedInput schema / properties / queueId / example
      Added value: +"507f1f77bcf86cd799439011"
  2. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Adds real value beyond the annotations: pagination behavior, the draft-vs-live sessionId branch, the POST endpoint and version header, and the required OAuth scope (socialplanner/category.readonly). The gap is the mismatch between the fetch/read framing and readOnlyHint=false, which the description never reconciles, plus no indication of what a queue item contains. Not a hard contradiction, but an agent could be misled about state effects.

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 core action and return behavior, then the sessionId variant, then endpoint/auth metadata. Four short lines with no filler; the endpoint/scope lines are metadata rather than prose but still earn their place for an agent assembling a call.

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 nested-body list tool with no output schema, the description covers pagination and the sessionId variant and discloses auth scope. What remains missing is the shape of a returned queue item and the meaning of the required queueId relative to a category, but the essentials for a correct invocation are present.

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 schema already documents skip, limit, itemId, sessionId, locationId and errorFilter. The description adds one piece of meaning beyond the schema by explaining that sessionId switches from live to draft items; the rest of the parameters (notably itemId centering and errorFilter) are left entirely to the schema.

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: fetching paginated items from a social category queue, with the queueId path param implied. It is distinguishable from siblings like ghl_social_fetch_queue_by_id (a single queue) and ghl_social_fetch_queues (the list of queues), but the description never explicitly names those alternatives, so the differentiation is inferential rather than stated.

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?

"Pass sessionId to get draft items from an edit session instead of live items" gives one concrete usage branch, which is genuinely helpful. However there is no guidance on when to choose this tool versus ghl_social_fetch_queue_by_id, ghl_social_fetch_slots, or ghl_social_fetch_edit_session_calendar, and no stated prerequisites for the edit-session flow.

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