Skip to main content
Glama
Sign In

dopost

by co.dopost.mcp
OverviewDiscussionsAdmin

Get Analytics Overview

get_analytics_overview
Read-onlyIdempotent

Read canonical account KPIs, account and platform rankings, coverage, comparisons, and freshness. Requires analytics:read and an active paid plan.

Input Schema

NameRequiredDescriptionDefault
daysNoRolling day range. Defaults to 30
endDateNoCustom range end date (ISO 8601); requires startDate
groupIdNo
metricsNo
platformNo
accountIdNo
startDateNoCustom range start date (ISO 8601); requires endDate
accountIdsNo
comparisonNoDefaults to "previous"
workspaceIdNoWorkspace ID from list_workspaces. Required for workspace-wide analytics when the connection has access to multiple workspaces; omit when accountId uniquely identifies the target
includeSeriesNoInclude daily series. Defaults to false and is limited to 90 days

Output Schema

NameRequiredDescriptionDefault
metaYes
overviewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / metrics / items / enum
      Previous value: -[
-  "followers",
-  "followerGrowth",
-  "views",
-  "reach",
-  "engagements",
-  "likes",
-  "comments",
-  "shares",
-  "saves",
-  "impressions",
-  "clicks",
-  "profileViews",
-  "profileVisits",
-  "replies",
-  "reposts",
-  "quotes",
-  "reactions",
-  "pinClicks",
-  "outboundClicks",
-  "pinClickRate",
-  "outboundClickRate",
-  "saveRate",
-  "engagementRate",
-  "videoViews",
-  "engagedViews",
-  "watchTimeMin",
-  "avgViewDuration",
-  "averageViewPercentage",
-  "follows",
-  "unfollows",
-  "subscribersGained",
-  "subscribersLost"
-]New value: +[
+  "followers",
+  "followerGrowth",
+  "views",
+  "reach",
+  "engagements",
+  "likes",
+  "comments",
+  "shares",
+  "saves",
+  "impressions",
+  "clicks",
+  "profileViews",
+  "profileVisits",
+  "replies",
+  "reposts",
+  "quotes",
+  "reactions",
+  "pinClicks",
+  "outboundClicks",
+  "pinClickRate",
+  "outboundClickRate",
+  "saveRate",
+  "engagementRate",
+  "videoViews",
+  "engagedViews",
+  "watchTimeMin",
+  "avgViewDuration",
+  "averageViewPercentage",
+  "follows",
+  "unfollows",
+  "subscribersGained",
+  "subscribersLost",
+  "googleSearchDesktopImpressions",
+  "googleSearchMobileImpressions",
+  "googleMapsDesktopImpressions",
+  "googleMapsMobileImpressions",
+  "websiteClicks",
+  "callClicks",
+  "directionRequests",
+  "messagingClicks",
+  "bookings",
+  "menuClicks"
+]
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "FACEBOOK",
-  "INSTAGRAM",
-  "INSTAGRAM_DIRECT",
-  "THREADS",
-  "PINTEREST",
-  "YOUTUBE",
-  "LINKEDIN",
-  "LINKEDIN_ORGANIZATION",
-  "BLUESKY",
-  "X",
-  "MASTODON"
-]New value: +[
+  "FACEBOOK",
+  "INSTAGRAM",
+  "INSTAGRAM_DIRECT",
+  "THREADS",
+  "PINTEREST",
+  "YOUTUBE",
+  "LINKEDIN",
+  "LINKEDIN_ORGANIZATION",
+  "BLUESKY",
+  "X",
+  "MASTODON",
+  "GOOGLE_BUSINESS"
+]
    • changedOutput schema / properties / meta / properties / filters / properties / metrics / items / enum
      Previous value: -[
-  "followers",
-  "followerGrowth",
-  "views",
-  "reach",
-  "engagements",
-  "likes",
-  "comments",
-  "shares",
-  "saves",
-  "impressions",
-  "clicks",
-  "profileViews",
-  "profileVisits",
-  "replies",
-  "reposts",
-  "quotes",
-  "reactions",
-  "pinClicks",
-  "outboundClicks",
-  "pinClickRate",
-  "outboundClickRate",
-  "saveRate",
-  "engagementRate",
-  "videoViews",
-  "engagedViews",
-  "watchTimeMin",
-  "avgViewDuration",
-  "averageViewPercentage",
-  "follows",
-  "unfollows",
-  "subscribersGained",
-  "subscribersLost"
-]New value: +[
+  "followers",
+  "followerGrowth",
+  "views",
+  "reach",
+  "engagements",
+  "likes",
+  "comments",
+  "shares",
+  "saves",
+  "impressions",
+  "clicks",
+  "profileViews",
+  "profileVisits",
+  "replies",
+  "reposts",
+  "quotes",
+  "reactions",
+  "pinClicks",
+  "outboundClicks",
+  "pinClickRate",
+  "outboundClickRate",
+  "saveRate",
+  "engagementRate",
+  "videoViews",
+  "engagedViews",
+  "watchTimeMin",
+  "avgViewDuration",
+  "averageViewPercentage",
+  "follows",
+  "unfollows",
+  "subscribersGained",
+  "subscribersLost",
+  "googleSearchDesktopImpressions",
+  "googleSearchMobileImpressions",
+  "googleMapsDesktopImpressions",
+  "googleMapsMobileImpressions",
+  "websiteClicks",
+  "callClicks",
+  "directionRequests",
+  "messagingClicks",
+  "bookings",
+  "menuClicks"
+]
    • changedOutput schema / properties / overview / properties / metrics / items / properties / key / enum
      Previous value: -[
-  "followers",
-  "followerGrowth",
-  "views",
-  "reach",
-  "engagements",
-  "likes",
-  "comments",
-  "shares",
-  "saves",
-  "impressions",
-  "clicks",
-  "profileViews",
-  "profileVisits",
-  "replies",
-  "reposts",
-  "quotes",
-  "reactions",
-  "pinClicks",
-  "outboundClicks",
-  "pinClickRate",
-  "outboundClickRate",
-  "saveRate",
-  "engagementRate",
-  "videoViews",
-  "engagedViews",
-  "watchTimeMin",
-  "avgViewDuration",
-  "averageViewPercentage",
-  "follows",
-  "unfollows",
-  "subscribersGained",
-  "subscribersLost"
-]New value: +[
+  "followers",
+  "followerGrowth",
+  "views",
+  "reach",
+  "engagements",
+  "likes",
+  "comments",
+  "shares",
+  "saves",
+  "impressions",
+  "clicks",
+  "profileViews",
+  "profileVisits",
+  "replies",
+  "reposts",
+  "quotes",
+  "reactions",
+  "pinClicks",
+  "outboundClicks",
+  "pinClickRate",
+  "outboundClickRate",
+  "saveRate",
+  "engagementRate",
+  "videoViews",
+  "engagedViews",
+  "watchTimeMin",
+  "avgViewDuration",
+  "averageViewPercentage",
+  "follows",
+  "unfollows",
+  "subscribersGained",
+  "subscribersLost",
+  "googleSearchDesktopImpressions",
+  "googleSearchMobileImpressions",
+  "googleMapsDesktopImpressions",
+  "googleMapsMobileImpressions",
+  "websiteClicks",
+  "callClicks",
+  "directionRequests",
+  "messagingClicks",
+  "bookings",
+  "menuClicks"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds entitlement context the annotations do not: the analytics:read scope and an active paid-plan requirement, which an agent must know before attempting the call. It stops short of mentioning rate limits or the 90-day cap on includeSeries (though the schema carries that).

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?

Two sentences, front-loaded with the data the tool returns and then the access prerequisite. Every clause earns its place and there is no filler. It is arguably too lean given the tool's complexity, but as a structure/concision judgment it is clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose and access requirements, and the existing output schema relieves it of explaining return values. However, for an 11-parameter, zero-required-parameter analytics tool with only 55% parameter coverage, the absence of any guidance on range selection, metric choice, or sibling routing leaves clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 11 parameters and only 55% schema description coverage, the description needs to compensate and does not. Beyond the word 'comparisons' loosely nodding at the comparison parameter, none of days, metrics, platform, accountIds, includeSeries, or the startDate/endDate pairing is clarified. The agent gets almost nothing here that the schema does not already supply.

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?

States a specific verb (Read) and enumerates the resource: canonical account KPIs, account and platform rankings, coverage, comparisons, and freshness. An agent can tell this is an account-level analytics rollup rather than a per-post tool. It does not, however, name any sibling (e.g., get_audience_analytics, get_content_insights, get_post_performance) to draw the boundary explicitly.

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 gives a hard gating condition (requires analytics:read and an active paid plan), which is genuinely useful for deciding whether the call is even feasible. It does not say when to prefer this tool over the other analytics siblings (audience, content insights, post performance), so selection guidance remains implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All dopost toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources