Skip to main content
Glama
Sign In

Postemi: Social Media Scheduler

by com.postemi
OverviewDiscussionsAdmin

open_postemi_panel

Read-only

Open the Postemi calendar and composer in the side panel of this conversation.

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": "open_postemi_panel"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoWhich part of the app to show first. Omit for the calendar.
draftNoOpen the composer filled in, so the user can adjust and schedule it by hand. Nothing is saved until they press the button.
postIdNoA postId from list_posts or create_post, to open the calendar with that post selected.

Output Schema

NameRequiredDescriptionDefault
viewYes
draftNo
postsNo
postIdYes
channelsNo
workspaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered by structured data. The description adds one piece of context beyond that — it opens UI in the conversation's side panel, i.e. a presentation action rather than a data change — but says nothing about the side effect of user interaction or what happens if a panel is already open.

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?

A single front-loaded sentence with zero filler or repetition. It is efficient, though so terse that it borders on under-specification rather than optimal brevity.

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?

An output schema exists and the nested draft object is well documented, so return values and parameter mechanics need not be repeated. Still, for a tool with three optional parameters, a nested object, and a near-identical sibling, the description leaves the selection decision and the panel-vs-non-panel distinction unaddressed.

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%: view has an enum with an explicit 'omit for calendar' default, draft is fully documented including 'nothing is saved until they press the button', and postId cites its source tools. The description itself contributes nothing about these parameters, so 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?

It names a specific verb ('Open') and a specific resource ('the Postemi calendar and composer') plus the target surface ('side panel of this conversation'), so the action is unmistakable. The only gap is that a sibling named open_postemi exists and the description never explains how this panel variant differs from it.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative open_postemi. The reader must infer from the name alone whether to use this or the non-panel version.

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