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

ghl-mcp-server-v2

by zackscriven

ghl_social_discard_edit_session

Cancel a social media queue edit session and delete all staged changes without altering the live queue.

Instructions

Discard edit session changes Cancels the edit session and deletes all staged changes without affecting the live queue. Endpoint: POST /social-media-posting/category/queues/{queueId}/edit/discard (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_discard_edit_session"
  }
}

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. Changed3 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"DiscardEditSessionDTO"
    • addedInput schema / properties / queueId / description
      Added value: +"Category queue ID"
    • addedInput schema / properties / queueId / example
      Added value: +"507f1f77bcf86cd799439011"
  2. First observedv2.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only and non-destructive, but the description adds the crucial nuance: all staged changes are deleted while the live queue is unaffected, plus the required OAuth scope (socialplanner/category.write). It does not say what the response contains or whether the sessionId becomes invalid afterwards, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences front-load the effect and the blast radius, followed by compact endpoint/scope metadata. No sentence is filler; the most important information (what is deleted and what is not) comes first.

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 mutation with no output schema, the description covers effect, blast radius and auth scope. It omits the lifecycle prerequisite (an active edit session created via start_edit_session) and any statement about the return value or post-call state, leaving an agent to infer the session's fate.

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% — queueId, sessionId, locationId and keepInDraft all have inline descriptions — so the description adds nothing parameter-level. Baseline 3 applies. Notably it does not explain the odd presence of keepInDraft on a discard operation, which would have been genuinely additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Discard edit session changes') and immediately clarifies semantics: cancels the session and deletes staged changes. An agent can distinguish it from ghl_social_save_edit_session and ghl_social_start_edit_session on the same queue without opening any schema.

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?

The 'without affecting the live queue' clause gives a clear condition/scope for choosing this over save_edit_session. However, it never states prerequisites (an edit session must already be open) or explicitly names the alternative/counterpart tool, so it stops short of explicit when/when-not guidance.

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