Skip to main content
Glama

get_best_time_to_post

Read-only

Answer "when should I post?", "what's my best time to post?", "when does my audience engage?" for a platform. Returns the day-of-week and hour slots (in the user's timezone) where posts have historically performed best, ranked by their posts' median engagement, each with how many posts it is based on (limit, default 3, max 10). With too few posts it says there isn't enough data yet. This is past results, not the posting schedule: to change when queued posts go out, use list_queue_schedule and add_queue_times.

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": {
      "platform": "<platform>"
    },
    "name": "get_best_time_to_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many time slots to return (default 3, max 10).
periodNoRolling window ending today. Default 30d. For any other window, pass start_date/end_date instead.
end_dateNoOptional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date.
platformYesRequired. The network to analyze.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
start_dateNoOptional. First day of a custom range, YYYY-MM-DD, in the user's timezone. Use for windows the presets don't cover: "last 14 days", "in March", "since Jan 1", "last year". Overrides `period`. Ranges can cover up to 366 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered; the description adds substantial behavior beyond that. It discloses the return shape (day-of-week and hour slots in the user's timezone, ranked by median engagement, with sample size per slot), the insufficient-data behavior ('it says there isn't enough data yet'), and the limit bounds.

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?

It is front-loaded with the user-intent phrasings that aid retrieval, then the return shape, then the disambiguation — a sensible order. The three quoted question variants are slightly redundant but serve query matching, so the length is largely justified.

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 analytics tool with no output schema, the description covers what an agent needs: ranking metric, timezone, sample-size caveat, small-data fallback, and the boundary with queue-scheduling tools. Nothing essential to calling or interpreting it correctly 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 coverage is 100%, so the schema already documents every parameter, including the period presets and the start_date override. The description's only parameter content is the limit default and max, which the schema already states, and the parenthetical placement ('each with how many posts it is based on (`limit`, default 3, max 10)') slightly blurs sample size versus slot count. Baseline 3 is appropriate.

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 gives a specific verb+resource (returns the day-of-week and hour slots where posts historically performed best) and frames it against the exact user questions it answers. It is clearly distinguishable from nearby siblings like get_analytics_summary or get_follower_history, which cover different metrics.

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 states when to use it ('when should I post?') and explicitly when NOT to: 'This is past results, not the posting schedule: to change when queued posts go out, use list_queue_schedule and add_queue_times.' That names the correct alternative tools by name and the condition that selects them.

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