Skip to main content
Glama

Get the best times to post

clipember_get_best_times
Read-onlyIdempotent

The days and hours when the user's own posts got the most views (weekday × hour in their time zone), from published posts of the last 90 days (or less, as the plan's analytics allow) that already have view counts. Each post counts relative to its own account's usual views, so a big account doesn't drown a small one. Below 10 such posts it says how many more are needed and suggests nothing — there are no made-up industry times. Filter by connectionId (clipember_list_platform_connections) or platform. Use it to suggest a time for clipember_create_post; the user picks.

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

Input Schema

NameRequiredDescriptionDefault
platformNo
timezoneNoIANA time zone; default — the user's own (Account settings)
connectionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "tiktok",
      -  "youtube_shorts",
      -  "instagram_reels",
      -  "bluesky",
      -  "facebook_reels",
      -  "threads",
      -  "linkedin"
      -]New value: +[
      +  "tiktok",
      +  "youtube_shorts",
      +  "instagram_reels",
      +  "bluesky",
      +  "facebook_reels",
      +  "threads",
      +  "linkedin",
      +  "pinterest"
      +]
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, yet the description still adds real behavioral context: the 90-day window truncated by plan analytics entitlement, the requirement that posts already have view counts, per-account normalization so large accounts don't dominate, and the below-10-posts behavior that returns a shortfall count instead of fabricated suggestions. That is exactly the extra information an agent could not get from structured fields.

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?

The core output definition is front-loaded in the first sentence, and each subsequent sentence carries a distinct fact (basis, normalization, threshold, filtering, downstream use). It is dense and slightly run-on with heavy em-dash/parenthetical nesting, but almost nothing is redundant.

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 does much of the return-value work: shape (weekday × hour), basis (relative per-post weighting), and the degenerate case (count of posts still needed). It leaves the exact response fields — e.g. whether a ranked list, a heatmap object, or per-slot scores are returned — unspecified, which is the main residual gap for a read tool.

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 description coverage is only 33% (only timezone is documented in-schema), so the description must compensate, and it does: it explains that platform/connectionId are filters and points to clipember_list_platform_connections for obtaining a connectionId, and it implies timezone governs the weekday × hour bucketing. It stops short of saying whether platform and connectionId are mutually exclusive or how they combine when both are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete artifact: 'The days and hours when the user's own posts got the most views (weekday × hour in their time zone)', plus the data basis (published posts, last 90 days, with view counts). It also distinguishes itself from generic industry-benchmark advice ('there are no made-up industry times'), though it never names a specific sibling such as clipember_get_account_analytics to contrast with.

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 an explicit downstream use ('Use it to suggest a time for clipember_create_post; the user picks') and routing for the ID filter ('Filter by connectionId (clipember_list_platform_connections) or platform'). What is missing is a when-not condition, e.g. that this is not a general performance report and that low-volume accounts should expect a null result rather than a recommendation.

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