Skip to main content
Glama
Sign In

Postemi: Social Media Scheduler

by com.postemi
OverviewDiscussionsAdmin

list_workspaces

Read-onlyIdempotent

List the Postemi workspaces this connection can act on, and which one it acts on now.

Call this when the user asks what workspaces they have, mentions a brand or client that does not match the current workspace, or when a channel they name is missing from list_integrations. Every other tool works on the CURRENT workspace only; switch_workspace changes it for connections made by signing in (a connection made with an MCP key stays in its own workspace).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description focuses on adding context the annotations cannot: that all other tools are scoped to the current workspace, and that switch_workspace only affects connections created by signing in, while MCP-key connections stay pinned to their own workspace. That auth-model nuance materially changes how an agent interprets a workspace switch.

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?

Two sentences, no filler: the capability and its scope come first, then the call conditions and alternatives. The parenthetical about MCP-key connections is compact and carries real information rather than restating the annotation set.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. Given the zero-param, read-only nature of the tool, the description covers everything an agent needs: what it returns conceptually, when to call it, and how the current-workspace model affects sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. Nothing in the text misrepresents the argument-free call.

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 first sentence names a specific verb and resource ('List the Postemi workspaces') and adds scope the name alone doesn't carry: the workspaces this connection can act on, plus which one is current. It is immediately distinguishable from siblings like switch_workspace and list_integrations, both of which are named in the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives three concrete triggers (user asks about workspaces, names a brand/client not matching the current one, or names a channel missing from list_integrations) and explicitly routes state changes to switch_workspace. It also states the key constraint that every other tool operates on the current workspace only, which is exactly the routing information an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Postemi: Social Media Scheduler toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources