Skip to main content
Glama

get_posting_slots

Read-onlyIdempotent

The next count real posting slots for this workspace, computed from its actual configured timezone/posting_days/posting_slots (Settings > Scheduling in the web app) or from when its followers are actually online — not a guess.

basis:

  • "auto" (default): the workspace's saved posting_slots if it has any; otherwise the connected account's peak online-follower hours (Instagram's online_followers, last 30 days); otherwise 18:00.

  • "settings": always the saved posting_slots (18:00 if none).

  • "audience": the peak online-follower hours; falls back like "auto" when the account has no audience data (under 100 followers, or Instagram returned none). Use it when the user asks when their followers are online or wants "the best time" rather than their usual slot. posting_days is honoured in every mode. source in the result says which one was actually used, and audience_peak_hours lists the top hours whenever audience data exists — mention them if they differ from the saved slot.

Refuses to run when the workspace has no timezone configured (timezone="" in list_workspaces' output): there is no reliable default to fall back to from an MCP connection (no browser timezone to borrow, unlike the web app), so defaulting to UTC or inferring one from the account would just be a different wrong guess than hardcoding IST. Ask the connected user for their real IANA timezone (e.g. "Asia/Kolkata", "America/New_York") and call update_scheduling_settings to save it first — that's a one-time setup per workspace, not something to ask on every scheduling request.

Each returned slot's scheduled_at is UTC-aware and ready to pass straight to schedule_reel/schedule_reels_bulk. weekday_local/time_local are there so you can confirm the slot with the user in their own timezone rather than UTC.

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

Input Schema

NameRequiredDescriptionDefault
basisNoauto
countNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
slotsYes
sourceNosettings
timezoneYes
audience_statusNo
audience_peak_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the full resolution chain (saved slots → online_followers last 30 days → 18:00), the hard refusal condition when timezone is empty and why no default is inferred, the audience-data availability threshold (under 100 followers), and that scheduled_at is already UTC-aware and directly consumable by schedule_reel/schedule_reels_bulk. This is behavior an agent could not infer from annotations.

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 purpose is front-loaded before the mode list, and the indented basis bullets make the modes scannable. Some justification prose ("a different wrong guess than hardcoding IST", "not something to ask on every scheduling request") is editorial but does carry actionable guidance, so only mild trimming would be warranted.

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?

Output schema exists, yet the description still gives the useful interpretive keys (`source`, `audience_peak_hours`, weekday_local/time_local for user confirmation). Combined with the documented failure mode and prerequisites, an agent has everything needed to call it correctly or recover when it refuses.

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?

Schema description coverage is 0%, so the description must carry parameter meaning; it does so well for `basis`, defining each of the three enum values and their fallbacks, and it notes posting_days is honoured in every mode. It adds little about `count` (bounds, whether large values are capped) or `workspace_id` beyond the refusal scenario, leaving a small gap.

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 states a specific verb and resource: it returns the next `count` real posting slots for a workspace, computed from configured settings or audience data rather than guessed. That scope is clearly distinguishable from siblings like schedule_reel (which consumes the slots) or update_scheduling_settings (which saves the config).

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 explicitly enumerates the three `basis` modes with their fallback chains and says when to prefer `audience` ("when the user asks when their followers are online or wants 'the best time'"). It also names the exact escalation path when the tool refuses: ask for the IANA timezone, then call update_scheduling_settings — a sibling it names outright.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources