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

ghl-mcp-server-v2

by zackscriven

ghl_social_reset_queue_item

Idempotent

Resets a specific social media queue item to its original state, discarding any modifications made. Use it to undo edits and restore the item's default content.

Instructions

Reset an item in a queue Resets a specific queue item to its original state, discarding any modifications made. Endpoint: PUT /social-media-posting/category/queues/{queueId}/items/{itemId}/reset (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_reset_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: +"ResetQueueItemDTO"
    • 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.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, openWorld=true, destructive=false. The description adds real value beyond them: it states that existing modifications are discarded, plus the write OAuth scope (socialplanner/category.write) and the API endpoint/version, which tells the agent what credentials and API surface are involved. Minor tension worth noting: 'discarding modifications' is effectively data-losing behavior while destructiveHint is false, though a reset to original state is defensible as non-destructive of the underlying item.

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 two lines, with endpoint and scope as supporting metadata. Slightly verbose in repeating 'queue' phrasing, but nothing is wasted.

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 three-parameter mutation with a nested body and no output schema, the description supplies the effect semantics, auth scope and endpoint. It does not say what the response contains or whether a sessionId is required for the reset, but the essentials for correct invocation are present.

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, itemId and the nested body fields (locationId, sessionId) are all documented with descriptions and examples in the schema. The description adds no parameter-level meaning beyond that, so the 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?

The description gives a specific verb (reset) and resource (queue item), and clarifies the effect: it restores a specific item to its original state and discards modifications. This distinguishes it in spirit from siblings such as ghl_social_update_queue_item or ghl_social_discard_edit_session, though it never names an alternative 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?

Usage is implied by 'discarding any modifications made' – an agent can infer this is the undo/revert path for a queue item. But there is no explicit when-to-use versus when-not-to-use, and no mention of the related update/clone/delete queue-item siblings.

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