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

ghl-mcp-server-v2

by zackscriven

ghl_social_update_queue

Idempotent

Update a social media posting queue's status, time slots, and skip dates to pause or resume scheduling and control when posts publish.

Instructions

Update queue settings or status Updates queue status (active/paused/deleted), time slots, or skip dates. Endpoint: PUT /social-media-posting/category/queues/{queueId} (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": {
      "queueId": "<queueId>",
      "body": "<body>"
    },
    "name": "ghl_social_update_queue"
  }
}

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. Changed9 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / status / description
      Previous value: -"Status of the Queue"New value: +"Status of the queue, e.g. 'paused'. (Spec bug override 2026-08-27: upstream declares this as an empty object schema. No enum documented; 'paused' is the spec example.)"
    • removedInput schema / properties / body / properties / status / example
      Removed value: -"paused"
    • changedInput schema / properties / body / properties / status / type
      Previous value: -"object"New value: +"string"
    • 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: +"UpdateCategoryQueueDTO"
    • 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?

Annotations already declare readOnly=false, idempotent=true, destructive=false, openWorld=true. The description adds real value by disclosing that 'deleted' is a reachable status (a soft-delete state not captured by destructiveHint) and by naming the exact endpoint, API version, and OAuth scope. It stops short of saying whether updates overwrite or merge existing settings, which matters for a PUT.

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?

Four short lines, front-loaded with the action and the changeable fields, then endpoint and auth metadata. Nothing is wasted, though the endpoint/spec-source line is more operational detail than agent-facing guidance.

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?

Covers purpose, changeable fields, auth scope, and the endpoint for a two-parameter nested mutation with no output schema. Merge-vs-replace semantics for the PUT body and the response shape are the only meaningful omissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3. The description earns above baseline by enumerating the status values 'active/paused/deleted' — the schema itself admits no enum is documented and that 'paused' is merely the spec example, so this closes a genuine gap. It also summarizes the time-slot and skip-date parameters in prose.

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 ('Update') and resource ('queue settings or status') and enumerates the three things it can change: status, time slots, skip dates. It's clearly the queue-level update rather than the item-level one, though it never names ghl_social_update_queue_item to make that contrast explicit.

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?

Describes what can be changed but offers no when-to-use guidance, no prerequisites beyond the OAuth scope line, and no explicit routing to alternatives like ghl_social_update_queue_item, ghl_social_create_queue, or ghl_social_reset_queue_item. The scope note implies required permissions, which is the only usage-adjacent context.

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