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

ghl-mcp-server-v2

by zackscriven

ghl_social_fetch_edit_session_calendar

Fetch a calendar preview of scheduled posts from draft items in an edit session to see how posts would be scheduled before saving changes.

Instructions

Fetch calendar view for an edit session Retrieves a calendar preview of scheduled posts based on draft items within an edit session. This shows how posts would be scheduled if changes were saved. Endpoint: POST /social-media-posting/category/queues/{queueId}/edit/calendar (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_edit_session_calendar"
  }
}

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

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

The description adds real behavioral context beyond the annotations: the result is hypothetical/projected from unsaved draft changes, not the live schedule. It does not mention that a valid edit session must already exist, nor any rate limits or side effects. There is also mild tension with the supplied readOnlyHint=false / idempotentHint=false, which a preview-style POST does not obviously warrant, though this is plausibly an artifact of the HTTP method being POST.

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 purpose is front-loaded in the first two sentences and the endpoint/OAuth lines are compact metadata appended afterward. Slightly more boilerplate than strictly needed, but nothing is padded or redundant.

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 two-parameter tool with a nested request body, the description covers what the call returns (a calendar preview of projected posts) and the OAuth scope required. Since no output schema exists, one could wish for more detail on the response shape, but the essential mental model is 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 description coverage is 100%, including descriptions for queueId, sessionId, startDate/endDate and the optional accountIds filter, so the schema does the heavy lifting. The description mentions the queueId path in the endpoint URL but adds no additional semantics for the nested body fields, which is the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Fetch calendar view for an edit session") and then clarifies exactly what is returned: a preview of scheduled posts derived from draft items in the edit session. That framing distinguishes it cleanly from siblings such as ghl_social_fetch_calendar_list and ghl_social_fetch_slots.

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?

"This shows how posts would be scheduled if changes were saved" gives a clear deciding context: call it while inspecting an edit session before committing. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it falls one step below full guidance.

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