Skip to main content
Glama
Sign In

SupaBird

by io.supabird.api
OverviewDiscussionsAdmin

Get Posting Slots

get_posting_slots
Read-onlyIdempotent

Show the user's posting calendar slots and which ones are free, filled, or already past.

When to call:

  • User asks what slots are available today, this week, or on a date.

  • Before scheduling into a slot, or when they ask how many posts they planned.

Pass date as YYYY-MM-DD (defaults to today in their slot timezone). days=1..7 to look ahead.

Do not invent times. Free slots can be filled with schedule_post using the slot's iso timestamp.

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

Input Schema

NameRequiredDescriptionDefault
dateNoLocal calendar date (YYYY-MM-DD). Omit for today.
daysNoHow many consecutive days to include, starting at date. Default 1.
social_setNoThe social set (brand) this is for: its name, id or one of its handles. Omit when the user has one set.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/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 the safety profile is covered. The description adds behavior beyond that: results are partitioned into free/filled/past, dates default to today in the user's slot timezone, and slots carry an iso timestamp usable by schedule_post. It stops short of describing ordering or how many slots per day are returned.

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?

Front-loaded with the purpose, then a scannable bulleted when-to-call list, then compact parameter notes. Slight redundancy with the schema in the 'days=1..7' and 'YYYY-MM-DD' restatements, but nothing is padded or confusing.

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?

For a three-parameter read tool with no output schema, the description adequately conveys what comes back (slot states) and how to act on it (schedule_post with the iso timestamp). The only meaningful omission is guidance on social_set for multi-brand users, which the schema covers only briefly.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by pinning 'today' to the user's slot timezone and clarifying that days is a look-ahead window starting at date. The social_set parameter is not addressed in the description at all, leaving one 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?

States a specific verb and resource ('Show the user's posting calendar slots') plus the state breakdown returned ('free, filled, or already past'), which lets an agent distinguish it from add_posting_slot, update_posting_slot, and remove_posting_slot without opening a schema.

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?

The 'When to call' block names two concrete triggers (asking about availability for today/this week/a date, and pre-scheduling checks or post counts) and explicitly routes the follow-up action to schedule_post. It also adds a negative guardrail, 'Do not invent times', which prevents a common failure mode.

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

All SupaBird 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