Skip to main content
Glama

Get Engagement Trends

get_engagement_trends
Read-onlyIdempotent

[Read · free] Get engagement time series for a profile with gap-filled buckets, rolling averages, and trend direction. Each bucket includes avg engagement, likes, comments, shares, and conversation rate. Useful for understanding whether engagement is growing or declining. Pass scope (a post_collections.id) to plot trends for 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_engagement_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNoOptional post_collections.id to scope the time series
date_toNoEnd date (ISO 8601)
date_fromNoStart date (ISO 8601)
profile_idYesTracked profile ID from list_profiles
granularityNoTime bucket granularityweekly
rolling_windowNoRolling average window size in buckets (default: 4 for weekly, 7 for daily, 3 for monthly)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds real behavioral value beyond them: outputs are gap-filled buckets with rolling averages and a trend direction, each bucket carrying avg engagement, likes, comments, shares, and conversation rate, plus a "[Read · free]" cost signal. It stops short of stating default date range or bucket count limits.

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?

Four compact sentences, front-loaded with the cost/read tag and the core purpose, then output composition, then the optional scoping parameter. No filler and no repetition of schema details beyond the one useful scope clarification.

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 return-value burden and does so by naming the bucket fields and trend direction. What remains unstated is the default date window when date_from/date_to are omitted and roughly how many buckets come back — modest gaps for a read-only, fully-schema'd tool.

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 description coverage is 100%, so granularity, date bounds, rolling_window defaults, and profile_id are already fully documented structurally. The description only re-touches `scope`, restating it as a post_collections.id that plots trends for a specific collection — marginal added meaning, consistent with the baseline 3.

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 specific verb and resource ("Get engagement time series for a profile") and enumerates the shape of the result — gap-filled buckets, rolling averages, trend direction, and per-bucket metrics. It does not distinguish itself from analytics siblings such as get_engagement_brief or get_posting_insights, so an agent cannot route between them from this text alone.

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?

"Useful for understanding whether engagement is growing or declining" implies the use case (trend analysis over time) but gives no explicit when-to-use vs. when-not, no prerequisites, and no named alternative. The scope parameter hint is the only routing signal, and it addresses a parameter rather than tool selection.

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