Skip to main content
Glama

Best time to post

best_time_to_post
Read-onlyIdempotent

Use this when someone asks when to post on Instagram, Facebook or TikTok in Kuala Lumpur, Penang, Johor Bahru, Singapore, Jakarta, Manila, Bangkok, New York, Los Angeles, Toronto, Vancouver, London, Sydney, Melbourne or Dubai (or one of those countries). Returns windows in that city's local time where two large 2026 studies (Sprout Social and Buffer) agree, shows where they disagree instead of picking one, and adds what we measured ourselves (restaurants and cafes in the Suara Restaurant Index, and Suara clients when there are enough posts). Do not use it for other cities, for a specific account's own best time, or to promise results.

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
cityNoCity or country, e.g. Kuala Lumpur, KL, Toronto or Malaysia
categoryNoKind of business, e.g. cafe or salon; optional
platformNoinstagram, facebook or tiktok; optional (all three when left out)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "city"
      -]New value: +[]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: it returns windows in the city's local time, surfaces study disagreement rather than collapsing it, and mixes in proprietary Suara data where sample size allows. It does not say what happens for an unsupported city or when client data is too thin beyond a passing hint.

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 trigger condition and followed by a single do-not-use sentence, which is the right structure. The long city enumeration bulks up sentence one and could be compressed, but every clause carries real routing information.

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?

With no output schema, the description carries the burden of explaining returns, and it does so at the right altitude: local-time windows, agreement and disagreement between two sources, and first-party restaurant/client data. A brief note on empty results or data-thin cities would make it fully complete.

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 would be 3. The description earns above baseline by narrowing the city parameter to an explicit supported list and noting countries are acceptable, and by implying platform defaults to all three when omitted via the schema note. Category semantics are still only illustrated by one example, not defined.

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 (best time to post) and scopes it to named cities for Instagram/Facebook/TikTok. It explicitly distinguishes itself from sibling my_best_times by ruling out a specific account's own best time, so an agent can route between them without reading either 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?

Opens with 'Use this when someone asks...' and closes with three explicit exclusions: other cities, a specific account's own best time, and promising results. The when/whom-not framing is unambiguous, and the exclusion of account-level timing points to my_best_times as the alternative.

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