Skip to main content
Glama

Get next free posting slot

get_next_free_slot

Next free queue slot of one account on any network, as {scheduledAt} (ISO time, null when no schedule is configured or every slot is booked). Pass it as scheduledAt of create_post. Requires the SCHEDULE_READ scope (key issued by the workspace owner).

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": {
      "channel": "<channel>",
      "accountId": "<accountId>"
    },
    "name": "get_next_free_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesNetwork of the account, e.g. INSTAGRAM (UPPERCASE canonical, lowercase accepted).
accountIdYesInternal account id on `channel` (from list_accounts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well by disclosing the return shape as {scheduledAt}, ISO time format, and null cases when no schedule exists or all slots are booked. It also discloses the required SCHEDULE_READ scope, though it does not explicitly state read-only/no-side-effect behavior.

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 a compact single sentence with the primary result front-loaded, followed by return semantics, integration guidance, and auth requirements. Every clause contributes useful information without repetition.

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?

For a two-parameter lookup tool with full schema coverage and no output schema, the description sufficiently explains the return value, null conditions, scope requirement, and intended downstream use. Nothing essential for correct invocation is missing.

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%, so channel and accountId are already well documented in the schema. The description adds only the contextual phrase "of one account on any network" and does not add syntax or selection details beyond the schema.

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 states a specific action and resource: "Next free queue slot of one account" on a network. It also distinguishes the result by naming its direct use with create_post, so an agent can tell what it returns and where it fits.

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

Usage Guidelines4/5

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

It explicitly says to pass the result as scheduledAt of create_post, which gives a clear usage path. It also states the SCHEDULE_READ scope requirement, though it does not specify when-not to use this versus related time-selection tools.

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