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

ghl-mcp-server-v2

by zackscriven

ghl_social_create_queue

Creates a draft social media category queue with publishing time slots; published posts are auto-added. Activate the queue through the update endpoint.

Instructions

Create a new category queue Creates a queue in draft status for a category. Published posts are auto-added. Use update endpoint to activate. Endpoint: POST /social-media-posting/category/queues (Version header: v3; source: v3/social-planner-v3.json) OAuth scopes: socialplanner/category.write

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_create_queue"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / body / properties / timeSlots / description
      Added value: +"Time slots defining when posts should be published"
    • addedInput schema / properties / body / properties / timeSlots / example
      Added value: +[
      +  {
      +    "dayOfWeek": 1,
      +    "time": "09:00"
      +  },
      +  {
      +    "dayOfWeek": 3,
      +    "time": "14:30"
      +  }
      +]
    • addedInput schema / properties / body / properties / timeSlots / items / title
      Added value: +"TimeSlotDTO"
    • addedInput schema / properties / body / title
      Added value: +"CreateCategoryQueueDTO"
  2. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already indicate this is a non-read-only, open-world, non-idempotent mutation. The description adds important behavior beyond annotations: the queue starts in draft, published posts are auto-added, activation requires a separate update call, and it specifies the OAuth scope.

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 description is short and front-loads the core action and draft-status behavior. Endpoint and OAuth details are compact and useful for invocation context, though the first line repeats the tool title.

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?

Given a mutation tool with rich schema coverage, no output schema, and annotations covering safety traits, the description supplies the key missing context: draft status, auto-add behavior, activation path, endpoint, and OAuth scope. It is complete enough to invoke correctly.

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 the nested body fields are already well documented. The description adds only high-level context about the category queue and does not explain parameter semantics beyond what the schema provides.

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 clearly states a specific verb and resource: create a category queue. It also distinguishes creation from activation by noting the update endpoint is used to activate. It does not explicitly differentiate itself from the related queue-item creation sibling.

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?

It gives clear usage context: the queue is created in draft status and must be activated via the update endpoint. It also notes that published posts are auto-added. It does not provide explicit when-not guidance or name alternative siblings such as queue-item tools.

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