Skip to main content
Glama

Get best times to post

get_best_times

Best times to post for one account on any network (YouTube included), ranked from its own history. Returns suggestions plus basis (METRICS = engagement numbers, PUBLISH_HISTORY = frequency only); an account with no posts returns an empty list with reason NO_HISTORY. GOOGLE BUSINESS PROFILE has no engagement data to rank by: it returns empty suggestions with reason NOT_SUPPORTED (not an error). 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_best_times"
  }
}

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.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does it well: it names the two ranking bases (METRICS vs PUBLISH_HISTORY), the empty-result behavior for both NO_HISTORY and NOT_SUPPORTED, and the SCHEDULE_READ permission requirement. These are the exact behaviors an agent needs to interpret a result or explain a failure.

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 tight sentences, front-loaded with what is returned and how it is ranked, then the edge cases, then the permission requirement. Parentheticals are used for the enum caveats rather than padding, and no sentence is redundant.

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?

No output schema exists, so the description must describe the response shape, and it does: suggestions plus a `basis` field, empty list with a `reason` code. Combined with the permission and channel-support notes, nothing an agent needs to call and interpret this tool is missing.

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 both parameters are already documented, and the baseline would be 3. The description still adds real meaning by clarifying that GBP is a selectable channel that returns NOT_SUPPORTED, and that coverage spans any network including YouTube — information not derivable from the enum alone.

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 resource ('best times to post'), an explicit scope ('one account on any network (YouTube included)'), and the ranking method ('ranked from its own history'). That method clause separates it from scheduling helpers like get_next_free_slot without needing to name them.

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 clear applicability context and two explicit exclusion paths: no posts yields an empty list with reason NO_HISTORY, and GBP yields NOT_SUPPORTED rather than an error. It stops short of routing the agent to an alternative when those exclusions fire, so it is strong but not a full when-to-use/when-not-to matrix.

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