Skip to main content
Glama

get_analytics_overview

Read-only

Get analytics overview with total posts, impressions, engagements, engagement rate, and per-platform breakdown. Use period for a rolling window (7d / 30d / 90d) or start_date + end_date for a custom range. The response echoes the resolved range and today's date — read those before assuming a year from training data (e.g. when the user says 'April', use the most recent April, not April from your training cutoff).

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

Input Schema

NameRequiredDescriptionDefault
tagNoPost numbers of the posts with this tag only (a tag name or id; comma separate several). Account numbers stay the whole account's. To compare tags with each other, use get_tag_analytics.
periodNoRolling window: 7d, 30d, 90d (default: 30d). Ignored if start_date/end_date are provided.
end_dateNoCustom end date. Same formats as start_date; "YYYY-MM" expands to the last day of the month.
start_dateNoCustom start date. Accepts "YYYY-MM-DD" (e.g. "2026-04-01") or "YYYY-MM" month-shorthand (e.g. "2026-04" → first of the month).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tag
      Added value: +{
      +  "description": "Post numbers of the posts with this tag only (a tag name or id; comma separate several). Account numbers stay the whole account's. To compare tags with each other, use get_tag_analytics.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: the response echoes the resolved range and today's date, plus a caution against assuming years from training data. With annotations carrying the safety burden, this is solid but not rich (no coverage of metric definitions or aggregation semantics).

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 sentences, each earning its place: metrics first, then date-window mechanics, then the resolution caveat. Front-loaded and free of filler.

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?

There is no output schema, and the description compensates by enumerating the returned top-level fields and the echoed range/date metadata. For a zero-required-parameter read tool with full schema coverage, an agent has everything needed to call it and interpret the result.

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%, including the period-vs-custom-range precedence and date format shorthands, so the schema does the heavy lifting (baseline 3). The description's added value is the interpretive hint about resolving ambiguous dates like 'April' against the echoed range, but the format and precedence details are repeated from the schema rather than extended.

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?

Names a specific verb and resource and enumerates the returned metrics (total posts, impressions, engagements, engagement rate, per-platform breakdown), which distinguishes it from post-level siblings. It never explicitly contrasts itself with account-level or post-level analytics tools, so sibling differentiation is only implicit.

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?

The description clearly explains the two mutually exclusive ways to specify a time window (rolling `period` vs `start_date`/`end_date`), which is real usage guidance. It says nothing about when to prefer this overview over get_account_analytics, get_posts_analytics, or get_tag_analytics, leaving tool-selection to inference from sibling names.

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