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

ghl-mcp-server-v2

by zackscriven

ghl_social_delete_queue_item

DestructiveIdempotent

Deletes a specific item from a social media category queue, removing unwanted queued posts by queue and item ID.

Instructions

Delete an item from a queue Deletes an item from a specific category queue. Endpoint: DELETE /social-media-posting/category/queues/{queueId}/items/{itemId} (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>",
      "itemId": "<itemId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_social_delete_queue_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesQueue item ID
queueIdYesCategory queue ID
sessionIdNoEdit session ID
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • addedInput schema / properties / itemId / description
      Added value: +"Queue item ID"
    • addedInput schema / properties / itemId / example
      Added value: +"507f1f77bcf86cd799439011"
    • addedInput schema / properties / queueId / description
      Added value: +"Category queue ID"
    • addedInput schema / properties / queueId / example
      Added value: +"507f1f77bcf86cd799439011"
  2. First observedv2.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds value the annotations don't: the OAuth scope requirement (socialplanner/category.write) and the exact endpoint. It still doesn't say whether related scheduled content is affected, but that is a minor residual gap.

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?

Short and front-loaded, with the endpoint and scope tucked after the purpose. The first sentence largely restates the title and the second repeats it, so there is a small amount of redundancy, but nothing is bloated.

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?

No output schema exists and annotations carry the safety profile, so remaining burden is low. Still, for a destructive operation it omits whether deletion is permanent, what happens to a queue slot or scheduled content tied to the item, and whether queueId must belong to the given location — all things the schema cannot express.

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 queueId, itemId, locationId and sessionId are already documented as property descriptions. The description adds only that the queueId refers to a 'category queue', which is marginal clarification. 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?

States a specific verb and resource ('Delete an item from a queue') and narrows it to a category queue item, which separates it from the many post-level delete siblings such as ghl_social_delete_post or ghl_social_delete_csv_post. It does not name a sibling explicitly, so differentiation is implied by the noun rather than spelled out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when this should be used instead of ghl_social_delete_post, ghl_social_bulk_delete_planner_posts, or ghl_social_reset_queue_item, all of which sit adjacent in the tool list. The agent must infer that 'queue item' means a slot entry rather than a scheduled post.

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