Skip to main content
Glama

get_analytics_summary

Read-only

Totals for the whole account or one platform over a period, not single posts. Answer questions about how an account is performing: followers, engagements, reach/impressions/views, and engagement rate, each with the period-over-period change. Call WITHOUT a platform for an everything-at-once roll-up (e.g. "how am I doing?", "followers?", "how did this month compare to last?"). Pass platform to focus on one network (e.g. "how's twitter doing?"). On LinkedIn it also answers "what kinds of reactions did I get?" with the Like/Celebrate/Support/Love/Insightful/Funny split for the period.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoRolling window ending today. Default 30d. For any other window, pass start_date/end_date instead.
end_dateNoOptional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date.
platformNoOptional. Omit for a cross-platform roll-up across every connected network.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
start_dateNoOptional. First day of a custom range, YYYY-MM-DD, in the user's timezone. Use for windows the presets don't cover: "last 14 days", "in March", "since Jan 1", "last year". Overrides `period`. Ranges can cover up to 366 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare this as a read-only, non-destructive, closed-world operation, so the description does not need to restate safety. It adds useful behavioral context by listing the metrics returned and noting period-over-period change, plus a special LinkedIn reaction breakdown. It does not discuss data freshness, permission requirements, or behavior when no data exists for a period.

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 description is front-loaded with scope and usage, and every sentence provides relevant context, including examples and the LinkedIn exception. It is slightly dense with example questions, but no sentence is wasted.

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?

There is no output schema, so the description usefully enumerates the returned metrics and period-over-period change, and it calls out the LinkedIn-specific reaction split. It is complete enough for an agent to call the tool correctly, though it could mention data availability or permission caveats.

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 all five parameters, including date ranges, presets, and workspace scoping, are already documented in the schema. The description reinforces the meaning of omitting versus passing platform, but that is largely duplicative of the schema's own platform description. Baseline 3 is appropriate because the schema carries most parameter semantics.

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?

The description states a specific verb and resource: totals for the whole account or one platform over a period. It explicitly excludes single-post analytics, which cleanly separates it from siblings such as get_post_analytics and list_top_posts.

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?

It gives explicit when-to-use guidance: omit platform for an everything-at-once roll-up, pass platform to focus on one network. It also provides natural-language example questions, and the phrase 'not single posts' routes single-post questions away from this tool.

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