Skip to main content
Glama
Sign In

ShortSync

by app.shortsync
OverviewDiscussionsAdmin

Get workspace analytics

get_workspace_analytics

Summarizes published-post analytics for a workspace over a rolling window: total posts, views, likes, comments, and shares, plus the same breakdown per platform. Numbers come from the cached per-post post_analytics table, NOT from live platform API calls. Filter to one platform by passing platform.

Freshness: if the workspace's analytics were last synced over an hour ago (or never), this call also starts a background sync and reports it in the response's sync field (status started or in_progress, plus last_synced_at). The numbers in that response are from the previous sync; call again in a few minutes for fresh ones. sync.status of free_plan_limit or daily_limit means no sync could run, so the numbers may not be current.

Analytics coverage: per-post analytics exist for YouTube, TikTok, Instagram, Facebook, LinkedIn (Company Pages), Threads, Bluesky, Pinterest (business accounts), Snapchat, Mastodon, Pixelfed, Reddit and Tumblr (Pixelfed, Reddit, Tumblr, Bluesky and Mastodon report no view counts). X has analytics only when the workspace has added its own X API key in Settings > Integrations (X bills each post read to the user's X developer account); without one, X posts come back unavailable with that reason. Google Business Profile has profile-level stats only (no per-post numbers). Telegram and Discord have no analytics at all.

Google Business Profile: posts always show 0 (Google has no per-post stats). When the workspace has a Google Business Profile connection, the response adds google_business_profile with profile views (Search + Maps impressions), website_clicks, call_clicks and direction_requests: window for the requested days (Google keeps ~30 days of daily data; window_fully_covered is false when the window starts earlier), last_30_days, and daily points. These profile stats are the Google Business numbers; the post totals stay at 0.

Dashboard parity note: numbers here match the ShortSync Overview dashboard exactly for TikTok, Snapchat, Threads, Mastodon, X, LinkedIn, Pinterest, Bluesky, Reddit, Tumblr and Pixelfed. For Instagram, Facebook, and YouTube the dashboard shows different (usually higher) numbers because it fetches account-level insights live from those three platforms, which count differently (Instagram video views include Reels impressions and reach; Facebook aggregates comments across the whole page; YouTube counts include Shorts feed views). This tool sums per-post cached metrics while the dashboard fetches account-level totals for those three platforms; get_post_analytics returns the numbers for a single post.

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days, counting from now. Default 30, max 365. The window is based on the post's published_at.
platformNoRestrict to one platform (instagram, youtube, tiktok, etc.). Omit to summarize across all.
workspace_idYesWorkspace to summarize. Required — get one from list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Despite annotations covering safety, the description adds substantial behavioral context: data comes from cached post_analytics rather than live APIs, stale data may trigger a background sync, and freshness statuses like free_plan_limit and daily_limit affect whether numbers are current. It also documents platform-specific coverage gaps, X API key requirements, and Google Business Profile limitations.

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 the core purpose and well structured into freshness, coverage, Google Business Profile, and dashboard parity sections. It is lengthy and has minor repetition, such as restating that Google Business Profile posts show 0, but the detail is largely justified by the tool's complexity.

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 annotations are minimal, so the description carries the full burden. It adequately explains the returned metrics, sync field behavior, platform-specific availability, Google Business Profile profile stats, and dashboard parity 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 days, platform, and workspace_id are already well documented in the schema. The description reinforces the platform filter and rolling-window concept but adds little parameter-specific meaning beyond the schema.

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?

States a clear verb and resource: summarizes published-post analytics for a workspace over a rolling window. It names the exact metrics and per-platform breakdown, and explicitly distinguishes itself from get_post_analytics for single-post numbers.

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

Usage Guidelines4/5

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

Gives clear context for filtering to one platform and points to get_post_analytics as the single-post alternative. It does not address other analytics siblings such as get_video_analytics or get_folder_analytics, so the when-to-use mapping is incomplete but still strong.

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

All ShortSync 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