Skip to main content
Glama
Sign In
Postoria MCP Server

Postoria MCP Server

Official
by postoria-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_queues

List publishing queues in a Postoria workspace using workspace ID. Returns queue IDs needed to add posts to the right queue.

Instructions

List publishing queues in a Postoria workspace. Returns queue IDs that should be used with add_post_to_queue.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_queues"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesPostoria workspace ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns queue IDs for use with add_post_to_queue, indicating a read-only behavior. However, it lacks details on permissions, rate limits, or side effects.

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?

The description is two sentences with no unnecessary words. It front-loads the purpose and immediately provides actionable context about the output. Every sentence adds value.

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?

Given the tool's simplicity (one parameter, no output schema), the description adequately explains what it does and what it returns. It could mention pagination or ordering if applicable, but it's sufficient for a basic list 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 coverage is 100% for the single parameter (workspace_id), with a description already in the schema. The tool description adds no additional semantic meaning beyond what the schema provides, meeting the baseline for high coverage.

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 clearly states the action (List), resource (publishing queues), and scope (in a Postoria workspace). It also explains the output's purpose (queue IDs for add_post_to_queue), distinguishing it from sibling tools like add_post_to_queue.

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 description implies usage context (before add_post_to_queue) but does not explicitly state when to use or avoid this tool, nor compare it to siblings like list_workspaces. Guidance is implied but not direct.

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