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

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_current_active_post_and_schedule_next

DestructiveIdempotent

Deletes a currently active scheduled post and automatically schedules the next available post in the queue, keeping your social posting cadence uninterrupted.

Instructions

Delete an active post and schedule the next one Deletes a post that is currently scheduled and automatically triggers the scheduling of the next available post in the queue. Endpoint: DELETE /social-media-posting/category/queues/{postId}/active-post (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": {
      "postId": "<postId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_social_delete_current_active_post_and_schedule_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesPost ID
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • addedInput schema / properties / postId / description
      Added value: +"Post ID"
    • addedInput schema / properties / postId / example
      Added value: +"507f1f77bcf86cd799439011"
  2. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=true, so the safety profile is covered. The description adds real value by disclosing the automatic rescheduling side effect and the required OAuth scope (socialplanner/category.write), but it does not say what happens when the queue is empty or whether the scheduled-next action is reversible.

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 is front-loaded in the first sentence, followed by endpoint and scope metadata. The first line duplicates the title verbatim, which is mild waste, but the rest is compact and earns its place.

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?

For a destructive mutation with no output schema, the definition covers endpoint, scope and the rescheduling side effect, but omits the outcome when no next post exists and gives no hint about the response. An agent could invoke it but could not predict the failure mode.

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

Parameters2/5

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

Schema description coverage is 100% but the descriptions are bare labels ('Post ID', 'Location ID'). The description in turn says nothing about either parameter, not even that postId refers to the queue's active post or how locationId scopes the request. Neither source adds semantic depth.

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 (delete the active post) plus a non-obvious secondary effect (auto-schedule the next queued post). This clearly distinguishes it from plain ghl_social_delete_post and ghl_social_delete_queue_item, though it never names those alternatives 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?

The context of use is implied by 'currently scheduled' active post in a queue, but there is no explicit when-to-use/when-not-to-use guidance, no mention of prerequisites (e.g. an active queue must exist), and no routing to sibling delete 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