Skip to main content
Glama

Cross-Network Analytics & Live Social Listening

analytics_query
Read-onlyIdempotent

Query cross-network engagement analytics (account_overview, post_metrics, audience_growth), compute AI-recommended optimal posting windows (best_times), or execute live real-time social listening (social_listen) across Bluesky, Hacker News, Dev.to, Reddit, and X. Use social_listen to discover live community threads, competitor mentions, and high-intent buyer questions matching any keyword query. Returns aggregated engagement metrics, X Smart Link cost savings, optimal CET/UTC posting slots, or live upstream social signals with direct thread URLs and author handles.

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": {
      "action": "<action>"
    },
    "name": "analytics_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch keyword, brand name, competitor handle, or buyer-intent phrase when running live `action: 'social_listen'` (e.g. 'MCP server social media API' or 'n8n AI agent workflow').
actionYesAnalytics or listening mode: 'account_overview' for cross-network KPIs, 'post_metrics' or 'post_detail' for individual post performance (including live YouTube viewCount, likeCount, commentCount, and publishedAt age in hours), 'audience_growth' for follower velocity, 'best_times' for highest-lift publishing windows, or 'social_listen' for live keyword/intent discovery.
postIdNoOptional post identifier (`post_...`) when inspecting granular metrics via `action: 'post_metrics'` or `'post_detail'`.
platformNoOptional social network filter to scope metrics or listening to a single platform.
accountIdNoConnected account id (`acc_...`). For Instagram/Facebook/Threads, returns live account insights plus recent posts with per-post insights.
postLimitNoMax recent posts (1-25) with per-post insights for Instagram/Facebook/Threads overviews.
profileIdNoBrand profile identifier (`prof_...`) to aggregate analytics for.prof_allometrik
periodDaysNoLookback window in days (e.g. 7, 30, 90) for aggregating impressions, engagements, and follower growth.
externalPostIdNoOptional native platform video/post ID (e.g. YouTube `videoId`) to fetch live `viewCount`, `likeCount`, `commentCount`, and `publishedAt` age in hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / accountId
      Added value: +{
      +  "description": "Connected account id (`acc_...`). For Instagram/Facebook/Threads, returns live account insights plus recent posts with per-post insights.",
      +  "type": "string"
      +}
    • addedInput schema / properties / postLimit
      Added value: +{
      +  "default": 10,
      +  "description": "Max recent posts (1-25) with per-post insights for Instagram/Facebook/Threads overviews.",
      +  "type": "number"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Analytics or listening mode: 'account_overview' for cross-network KPIs, 'post_metrics' for individual post performance, 'audience_growth' for follower velocity, 'best_times' for highest-lift publishing windows, or 'social_listen' for live keyword/intent discovery."New value: +"Analytics or listening mode: 'account_overview' for cross-network KPIs, 'post_metrics' or 'post_detail' for individual post performance (including live YouTube viewCount, likeCount, commentCount, and publishedAt age in hours), 'audience_growth' for follower velocity, 'best_times' for highest-lift publishing windows, or 'social_listen' for live keyword/intent discovery."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "account_overview",
      -  "post_metrics",
      -  "audience_growth",
      -  "best_times",
      -  "social_listen"
      -]New value: +[
      +  "account_overview",
      +  "post_metrics",
      +  "post_detail",
      +  "audience_growth",
      +  "best_times",
      +  "social_listen"
      +]
    • addedInput schema / properties / externalPostId
      Added value: +{
      +  "description": "Optional native platform video/post ID (e.g. YouTube `videoId`) to fetch live `viewCount`, `likeCount`, `commentCount`, and `publishedAt` age in hours.",
      +  "type": "string"
      +}
    • changedInput schema / properties / postId / description
      Previous value: -"Optional post identifier (`post_...`) when inspecting granular metrics via `action: 'post_metrics'`."New value: +"Optional post identifier (`post_...`) when inspecting granular metrics via `action: 'post_metrics'` or `'post_detail'`."
  3. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / action / description
      Added value: +"Analytics or listening mode: 'account_overview' for cross-network KPIs, 'post_metrics' for individual post performance, 'audience_growth' for follower velocity, 'best_times' for highest-lift publishing windows, or 'social_listen' for live keyword/intent discovery."
    • addedInput schema / properties / periodDays / description
      Added value: +"Lookback window in days (e.g. 7, 30, 90) for aggregating impressions, engagements, and follower growth."
    • addedInput schema / properties / platform / description
      Added value: +"Optional social network filter to scope metrics or listening to a single platform."
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "x",
      -  "linkedin",
      -  "instagram",
      -  "facebook",
      -  "threads",
      -  "tiktok",
      -  "youtube",
      -  "bluesky",
      -  "mastodon",
      -  "farcaster",
      -  "reddit",
      -  "pinterest",
      -  "google_business",
      -  "telegram",
      -  "discord",
      -  "ghost",
      -  "wordpress",
      -  "webflow"
      -]New value: +[
      +  "x",
      +  "linkedin",
      +  "bluesky",
      +  "instagram",
      +  "facebook",
      +  "threads",
      +  "tiktok",
      +  "youtube",
      +  "reddit",
      +  "pinterest",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "google_business",
      +  "ghost",
      +  "wordpress",
      +  "webflow",
      +  "whatsapp"
      +]
    • addedInput schema / properties / postId / description
      Added value: +"Optional post identifier (`post_...`) when inspecting granular metrics via `action: 'post_metrics'`."
    • addedInput schema / properties / profileId / default
      Added value: +"prof_allometrik"
    • addedInput schema / properties / profileId / description
      Added value: +"Brand profile identifier (`prof_...`) to aggregate analytics for."
    • changedInput schema / properties / query / description
      Previous value: -"Keyword or brand query for live social_listen"New value: +"Search keyword, brand name, competitor handle, or buyer-intent phrase when running live `action: 'social_listen'` (e.g. 'MCP server social media API' or 'n8n AI agent workflow')."
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description adds useful context by noting social_listen hits live upstream networks and that results include thread URLs and author handles, but it doesn't discuss rate limits, latency, freshness, or failure behavior for a live-crawl action.

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?

Three front-loaded sentences: capability list, the key listening use case, then return payloads. Dense but every sentence carries information; the parenthetical action enumerations are slightly repetitive with the schema enum.

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?

Given nine parameters, no output schema, and read-only annotations, the description sufficiently covers what the tool returns (aggregated metrics, cost savings, CET/UTC slots, live signals) across all six action modes. Minor gap: no guidance on combining periodDays/platform with social_listen or on default profile behavior.

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%, with per-parameter descriptions and enums for action and platform, so the schema does the heavy lifting. The description adds some mapping (social_listen needs a keyword query) but no syntax, casing, or interaction rules (e.g. postId vs externalPostId) 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 specific verb+resource (query cross-network engagement analytics) and enumerates the action modes it covers (account_overview, post_metrics, audience_growth, best_times, social_listen) across named platforms. Distinguishes itself from siblings like traffic_analytics and accounts_manage by being the social-metric/listening surface.

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?

The description gives positive routing guidance ('Use social_listen to discover live community threads, competitor mentions, and high-intent buyer questions') and maps each action to an output type. It doesn't state when NOT to use it, and doesn't name sibling alternatives such as traffic_analytics for site-side metrics, which leaves some ambiguity.

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