Skip to main content
Glama

SocialCaptain Creator Tools

Best time to post on Instagram or TikTok

best_time_to_post
Read-onlyIdempotent

Best days and hours to post on Instagram or TikTok, in a chosen time zone. For Instagram it returns a starting schedule (three posting hours per day and the five strongest slots) for one of 10 niches, plus what large published studies found. For TikTok it returns what the published studies found, by day. Times are given for the audience's time zone, optionally shown in another one. A rule of thumb to test against your own analytics, not data from an account.

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

Input Schema

NameRequiredDescriptionDefault
nicheNoInstagram only: the account's niche. Default general. Ignored for TikTok, whose studies are not split by niche.
platformNoPlatform. Default instagram.
timezoneNoIANA time zone where the audience lives, for example America/New_York or Asia/Kolkata. Default UTC.
display_timezoneNoIANA time zone to show the times in. Default: the audience's time zone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With annotations already declaring read-only, idempotent, non-destructive behavior, the description adds substantial value by explaining the exact return shape: Instagram gets a starting schedule with three hours per day plus five strongest slots and study findings, while TikTok returns study findings by day. It also clarifies time-zone behavior and the important limitation that results are generic guidance, not account data.

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 front-loaded with the core purpose, then efficiently differentiates Instagram and TikTok output, time-zone handling, and the key caveat. Every sentence contributes useful information without repetition or clutter.

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 read-only recommendation tool with full schema coverage and no output schema, the description does everything needed: it explains what is returned on each platform, how time zones are handled, the niche scope, and the limitation that this is not account-derived data.

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 coverage is 100%, and the schema already documents niche, platform, timezone, and display_timezone. The description reinforces that niche applies only to Instagram and that times are shown in the audience time zone with an optional display time zone, but it adds little beyond the schema descriptions.

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 clearly states the tool returns best posting days and hours for Instagram or TikTok, and it explicitly distinguishes the output from account-specific analytics data. An agent can tell this is a recommendation/study-based tool rather than an account statistics tool.

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 gives clear usage context: use it as a rule of thumb to test against your own analytics, and it explicitly says it is not data from an account. It does not name sibling alternatives such as instagram_statistics, so the routing guidance is strong but not fully explicit.

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