Skip to main content
Glama
AdaptlyPost

AdaptlyPost

Official

Get Analytics Timeseries

get_analytics_timeseries
Read-onlyIdempotent

Retrieves views, likes, comments, shares, followers and engagement rate bucketed by day, week or month across a date range, so you can see how metrics trend over time.

Instructions

Views, likes, comments, shares, followers, posts published and engagement rate bucketed by day (default), week or month across the window, for trend questions such as "how are views moving" or "when did followers jump". Returns { points } with one { date, ...metrics } per bucket; followers is the latest count at the end of the bucket, the other counters sum posts published inside it, and a metric no selected platform reports is null. Use get_analytics_overview for totals and list_post_analytics to see which posts drove a spike.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_analytics_timeseries"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd of the reporting window (ISO 8601). Must not be earlier than from
fromYesStart of the reporting window as an ISO 8601 date or instant (e.g. "2026-08-01"). Metrics cover posts published between from and to; the comparison window is the same length immediately before from
platformsNoRestrict to these platforms; omit for every platform with analytics. MASTODON, TELEGRAM, TUMBLR and WORDPRESS have no analytics and are ignored. GOOGLE_BUSINESS reports location impressions only, with no per-post numbers
granularityNoHow much time each point in the series covers: one day, one week or one month. Omit for one point per day
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another
connectionIdsNoRestrict to these accounts, by the account id from list_accounts; omit for every account

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with points: one { date, views, likes, comments, shares, followers, postsCount, engagementRate } per bucket, in date order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.22.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious semantics beyond them: followers is a point-in-time count at bucket end, other counters sum posts published inside the bucket, and unreported metrics come back as null. It stops short of pagination/limits or how comparison windows surface in the response, which keeps it below a 5.

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?

Front-loads the metric list and granularity, then the return shape, then the sibling routing — a sensible order with no filler sentences. It is dense enough that a reader must work through three long clauses, but each clause carries distinct information.

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?

For a 6-parameter, enum-bearing, read-only analytics tool with an output schema, the description covers purpose, aggregation semantics, null behavior and sibling routing. Nothing an agent needs in order to call it correctly is missing.

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 100%, so from/to, granularity, platforms, workspaceId and connectionIds are already documented, and the description largely restates the DAILY default. It adds only marginal parameter-level meaning (a metric no selected platform reports is null), which is closer to output interpretation than argument semantics, so baseline 3 applies.

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?

Names the specific metrics returned (views, likes, comments, shares, followers, posts published, engagement rate) and the bucketing dimension (day/week/month) across a window. It also distinguishes itself from get_analytics_overview (totals) and list_post_analytics (per-post attribution), so an agent can pick it without opening a schema.

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

Usage Guidelines5/5

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

Explicitly scopes usage to trend questions ('how are views moving', 'when did followers jump') and names two alternatives with the condition that selects each (totals vs. spike attribution). Nothing is left to inference about when to reach for this tool.

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