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

ghl-mcp-server-v2

by zackscriven

ghl_social_save_edit_session

Applies staged social media queue edits to the live queue and closes the edit session, with an option to keep the queue in draft instead of activating it.

Instructions

Save edit session changes Applies all staged changes to the live queue and closes the edit session. Endpoint: POST /social-media-posting/category/queues/{queueId}/edit/save (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_save_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: +"SaveEditSessionDTO"
    • 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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds real context beyond that: it names the required OAuth scope (socialplanner/category.write), the concrete effect on the live queue, and that the session is terminated. It stops short of saying whether the save is reversible or what happens on an expired/invalid session.

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?

Front-loaded with the action and its effect in two sentences, then the machine-generated endpoint metadata. The OAuth scope line is valuable; the 'Version header / source: v3/social-planner-v3.json' fragment is largely boilerplate but small.

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?

For a mutation tool with no output schema, annotations already carry the safety profile and the description covers the auth scope and post-call state (session closed, queue live). Only failure/expiry behavior and the exact return payload are unaddressed, which is a minor gap.

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 coverage is 100%; both queueId and the nested body fields (sessionId, locationId, keepInDraft) are documented in the schema, including the DRAFT-state caveat for keepInDraft. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

The description uses a specific verb ('Save/Applies') and resource ('edit session changes' / 'staged changes to the live queue') and states the side effect of closing the session. That effect distinguishes it from ghl_social_discard_edit_session and ghl_social_start_edit_session without the agent needing to open another schema.

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 phrase 'Applies all staged changes to the live queue and closes the edit session' implies the prerequisite of an open session and that this is the commit step, but it never names the sibling alternatives (discard vs save) or states when to use this instead of ghl_social_update_queue. Usage is inferable rather than explicit.

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