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

ghl-mcp-server-v2

by zackscriven

ghl_social_fetch_slots

Fetch paginated slot details (scheduled time, skip status) for social planner queue items. Use after mutations to refresh draft or live slots, with optional pagination.

Instructions

Fetch slot information for queue items Returns paginated slot information (scheduledDateTime, isSkipped) for queue items. Pass sessionId to get slots for draft items, or omit for live items. Call this after mutations to refresh slot data. Endpoint: POST /social-media-posting/category/queues/{queueId}/slots (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_slots"
  }
}

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: +"FetchSlotsDTO"
    • 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.6/5.0
Behavior3/5

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

Adds useful context beyond the annotations: pagination behavior, the fields returned, the underlying endpoint, and the required OAuth scope (socialplanner/category.readonly). However, it never reconciles the tension between "fetch" semantics and the annotations' readOnlyHint=false and idempotentHint=false, so an agent cannot tell whether this POST-based read mutates anything or is safe to retry.

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?

The core behavior, the sessionId rule, and the after-mutation call pattern are front-loaded, with endpoint and scope metadata trailing as reference. There is mild redundancy between the title-like first line and the second sentence, but nothing wasteful.

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?

With no output schema, the description usefully names the returned fields (scheduledDateTime, isSkipped) and flags pagination, and the nested body's locationId is covered by the schema. It could still say more about the pagination envelope (totals, cursors) for a paginated read, which keeps it from a 5.

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%, and every parameter (skip, limit, sessionId, locationId) is documented in the schema itself. The description's only parameter-related statement is the sessionId draft-vs-live rule, which essentially restates the schema's own text, so it adds little beyond the structured fields.

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 slot information for queue items) and even enumerates the returned fields (scheduledDateTime, isSkipped), so the agent knows exactly what comes back. It distinguishes itself implicitly from queue-item listings by saying it returns slots for items rather than the items themselves, but never names or contrasts with a sibling such as ghl_social_fetch_queue_items.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Pass sessionId to get slots for draft items, or omit for live items" and "Call this after mutations to refresh slot data" give concrete selection and timing guidance. What's missing is an explicit alternative or exclusion (e.g., use fetch_edit_session_calendar for the full edit-mode view), so it stops short of the when-to-use/when-not bar.

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