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

ghl-mcp-server-v2

by zackscriven

ghl_social_clone_queue_item

Duplicates an existing social media queue item at a specified order position, requiring an active edit session.

Instructions

Clone a queue item Duplicates an existing queue item at a specified order position. Requires an active edit session. Endpoint: POST /social-media-posting/category/queues/{queueId}/items/{itemId}/clone (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>",
      "body": "<body>"
    },
    "name": "ghl_social_clone_queue_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).
itemIdYesQueue item ID
queueIdYesCategory queue ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • addedInput schema / properties / body / title
      Added value: +"CloneQueueItemDTO"
    • 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

A3.6/5.0
Behavior4/5

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

Annotations cover the safety profile (non-readOnly, non-destructive, non-idempotent, openWorld), so the bar is lower. The description adds an invocation-critical constraint the annotations do not carry: an active edit session must exist before cloning. It does not explain what happens on a missing/expired session or whether repeating the call duplicates twice despite idempotentHint=false.

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 behavior (what it does, the session prerequisite) is front-loaded before the endpoint/OAuth metadata, and nothing is padded. The endpoint/version/source lines are boilerplate but compact.

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?

Given a mutation with a nested required body and no output schema, the definition covers the session prerequisite but leaves gaps: it does not say what is returned (the cloned item or just an ack) or whether the clone inherits the source item's content/accounts. Adequate but not complete for a clone operation.

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%, including per-field descriptions for order, sessionId, and locationId, so the schema does the heavy lifting. The description's only parameter-adjacent content ('specified order position') restates what the order field already documents.

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 (clone/duplicate) and resource (queue item), plus the placement semantics ('at a specified order position'). It is distinguishable from create/update queue item siblings by name and verb, though the description 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 prerequisite 'Requires an active edit session' is genuinely useful invocation guidance. However, there is no explicit statement of when to clone versus creating a new item, nor what to do if no session exists (start_edit_session), so usage is only implied.

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