Skip to main content
Glama
Upload-Post

Upload-Post

Official

Best times to post

get_best_times
Read-only

Retrieve the best hours to publish for a connected account, ranked by audience activity and post history, with source and confidence. Use it to pick posting times per platform and timezone.

Instructions

Best hours to publish for one connected account, from its own audience and post history. Answers best_times (hour, score), by_hour, by_day (0 = Monday), source (audience_activity, account_posts, upload_post_history or none) and confidence; with too little history source is none and best_times is empty. Results are cached for 24 hours (YouTube 7 days). To fill the posting queue with these hours automatically, use update_queue_settings with slots "auto".

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

Input Schema

NameRequiredDescriptionDefault
topNoHow many best hours to return. Default 5.
refreshNoRecompute when the cached answer is at least 24 hours old (YouTube 7 days).
page_urnNoLinkedIn only: organization Page id or URN managed by the connection.
platformYes
timezoneNoIANA timezone for the hours, e.g. Europe/Madrid. Default: the queue's timezone, else UTC.
facebook_page_idNoFacebook only: Page id managed by the connection.
profile_usernameYesUpload-Post profile name.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations by disclosing caching windows (24 hours, YouTube 7 days), the precise degradation behavior when history is thin ('source is none and best_times is empty'), and the enumerated source values. That is exactly the operational context an agent needs to interpret stale or empty results.

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?

Three sentences, front-loaded with purpose, then return shape, then the cache caveat, then the alternative. Every clause carries information; nothing is filler despite the density.

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?

Covers purpose, output shape, failure mode, caching, and the follow-on tool for a moderate-complexity 7-parameter read tool. Enumerating return fields is slightly redundant given an output schema exists, but it costs little and the behavioral picture is effectively complete.

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 86%, so defaults for top, timezone, refresh, page_urn and facebook_page_id are already documented in the schema. The description adds meaning only to refresh by tying it to the stated cache windows; it adds nothing for top, timezone, or the page-id parameters, so it sits at the high-coverage baseline.

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 hours to publish') and pins the scope to 'one connected account, from its own audience and post history' — immediately separating it from analytics or queue tools. An agent knows exactly what it gets back without opening the schema.

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?

Gives an explicit forward path — 'To fill the posting queue with these hours automatically, use update_queue_settings with slots "auto"' — which routes the agent to the right sibling for the follow-on action. It stops short of saying when NOT to call it (e.g., it needs an existing post history), so it is context-rich but not fully exclusive.

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

Deploy Server

Other Tools