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

ghl-mcp-server-v2

by zackscriven

ghl_social_fetch_queue_by_id

Read-onlyIdempotent

Retrieve a category queue's details by its unique ID, including the count of posts with errors, to inspect queue status for a location.

Instructions

Fetch a category queue by ID Retrieves the details of a single category queue by its unique ID. The response includes a count of posts within the queue that have errors. Endpoint: GET /social-media-posting/category/queues/{queueId} (Version header: v3; source: v3/social-planner-v3.json) OAuth scopes: socialplanner/category.readonly

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>",
      "locationId": "<locationId>"
    },
    "name": "ghl_social_fetch_queue_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
queueIdYesCategory queue ID
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • 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 readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description still adds value beyond them: the OAuth scope (socialplanner/category.readonly), the concrete endpoint and version header, and the non-obvious fact that the response carries a count of posts with errors. It omits failure behavior (e.g., what happens for a missing/foreign queueId), which keeps it below a 5.

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 first line front-loads the action and the second sentence adds the retrieval detail, so it is well ordered. There is mild redundancy between the title, the first line and 'Retrieves the details of a single category queue', plus endpoint/source metadata that is useful but slightly bulky.

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?

With only two required parameters, 100% schema coverage and annotations covering the safety profile, the description supplies the remaining context an agent needs: endpoint, scope, and one notable response field. Since there is no output schema, not enumerating all returned fields is a minor gap rather than a blocking one.

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%, with both queueId and locationId documented with examples, so the baseline is 3. The description adds only that queueId is a 'unique ID' and appears in the path template; it gives no additional meaning for locationId or the relationship between the two.

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 states a specific verb and resource ('Fetch a category queue by ID', 'Retrieves the details of a single category queue') and the endpoint path makes the single-resource scope explicit. It does not name the sibling list tool (ghl_social_fetch_queues) as the alternative, so the differentiation from siblings is left implicit rather than stated.

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 only implied: 'by its unique ID' suggests it is for known-ID lookups rather than enumeration, and the required queueId/locationId pair signals a scoped fetch. There is no explicit when-to-use, when-not-to-use, or pointer to ghl_social_fetch_queues for listing, which an agent would need to choose correctly among many social queue 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