Skip to main content
Glama

Get Posting Insights

get_posting_insights
Read-onlyIdempotent

[Read · free] Get optimal posting patterns for a profile: best day of week, best hour, format performance breakdown, and character length sweet spot. Includes full metric breakdown (likes, comments, shares, conversation rate) for every bucket. All metrics relative to the user's own baseline. Pass scope (a post_collections.id) to recompute the patterns against a specific collection.

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_id": "<profile_id>"
    },
    "name": "get_posting_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoOptional post_collections.id to scope the analysis
date_toNoEnd date (ISO 8601)
date_fromNoStart date (ISO 8601)
profile_idYesTracked profile ID from list_profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag read-only, idempotent, closed-world and non-destructive, so the safety bar is low. The description adds genuinely non-obvious behavior: every metric is normalized to the user's own baseline, and the scope parameter triggers a recomputation rather than a simple filter. It also flags the call as free, which no annotation conveys.

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?

Dense and front-loaded: the cost/safety tag and the core purpose come first, followed by the returned dimensions and the scope caveat. Two long sentences with no filler, though the metric enumeration is slightly list-heavy.

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 describing return content, and it does so by naming each insight bucket and the underlying metrics. Only the date_from/date_to semantics (window defaults, timezone) go unmentioned, which is a minor gap given they are documented in the schema.

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 baseline is 3, but the description goes beyond it by explaining that `scope` is a post_collections.id and that it re-runs the analysis against that collection rather than filtering results. The date range parameters are left to the schema, which is acceptable given full coverage.

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 ("Get optimal posting patterns for a profile") and enumerates exactly what comes back: best day of week, best hour, format breakdown, character-length sweet spot. An agent can distinguish this from preview_posting_insights or get_topic_insights without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the content (use it to learn optimal posting times/formats) and the scope parameter is given a clear use case. However, it never states when to choose this over the sibling preview_posting_insights or get_topic_insights, so the agent must infer the boundary.

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