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

ghl-mcp-server-v2

by zackscriven

ghl_social_fetch_calendar_list

Retrieve scheduled social posts in a calendar view for a date range, with optional filters by category and account.

Instructions

Get scheduled posts calendar view Returns scheduled posts from active queues within a date range. Supports filtering by categories and accounts. Endpoint: POST /social-media-posting/category/queues/list/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": {
      "body": "<body>"
    },
    "name": "ghl_social_fetch_calendar_list"
  }
}

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: +"CalendarListDTO"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

The description declares a pure read ('Get...', 'Returns scheduled posts'), but the annotations set readOnlyHint=false, so the two structured signals disagree about whether state can be modified. The description does add real value beyond annotations by disclosing the required OAuth scope (socialplanner/category.readonly) and the 'active queues' scoping, but the read/write conflict remains unresolved in the text.

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 operational content is front-loaded in two short sentences, with endpoint and scope metadata appended as compact context. No sentence is wasted, though the endpoint/version boilerplate is lower-value than a note on return shape.

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 and a nested body object, the description never says what the calendar view returns (post list shape, per-day grouping, pagination). It is adequate to call the tool but incomplete for an agent that must consume or page through the results.

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 startDate, endDate, categoryIds and accountIds are already documented in the schema, including the 'empty means all posts' behavior. The description only restates those filters at a high level and adds nothing about ID formats or date semantics, so baseline 3 applies.

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?

The description names a specific verb and resource ('Get scheduled posts calendar view', 'Returns scheduled posts from active queues') and adds scope (date range, category and account filters). It is clear enough to distinguish from siblings like fetch_queue_items or get_posts, though it never names an alternative explicitly.

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?

It implies usage: a date range is required and filters are optional, and it discloses the endpoint and OAuth scope for context. However, it gives no guidance on when to choose this calendar view over the sibling listing tools (ghl_social_get_posts, ghl_social_fetch_queue_items, ghl_social_fetch_slots), leaving that inference to the agent.

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