Skip to main content
Glama

Sociality.io Social Media MCP

Get account stats

social_account_stats_list
Read-only
Use this when the user asks how one of their own accounts performed over a date range: followers and follower growth, views, reach, likes, comments, shares and the other account-level metrics the channel provides, per day, week or month. Needs an account ID from social_accounts_list. Returns one row per period; the metric names differ by channel. For single posts or engagement rate per post, use social_account_posts_list. For competitors, use social_competitor_stats_list.

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": {
      "account_id": "<account_id>",
      "since": "<since>",
      "until": "<until>"
    },
    "name": "social_account_stats_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceYesFirst day of the range, YYYY-MM-DD, for example 2026-10-01.
untilYesLast day of the range, YYYY-MM-DD, included. The last 1 to 3 days may not be available yet, depending on the channel; whatever data exists is returned.
periodNoGroup the rows by day (default), week or month.
account_idYesThe account ID from social_accounts_list.

Output Schema

NameRequiredDescriptionDefault
accountNo
_envelopeYesVersioned response envelope metadata.
account_statsYesList of account stats for the given period.
action_requiredNoPresent only when a user action is required before this request can be answered. The data block is empty and no credits were charged. Do not re-call this tool with different arguments or a wider date range; the workspace needs a change first, unless the action says how to adjust the call or names a tool that makes the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / account_id / description
      Previous value: -"The ID of the account to get analytics for."New value: +"The account ID from social_accounts_list."
    • changedInput schema / properties / period / description
      Previous value: -"Aggregation period: day, week, or month."New value: +"Group the rows by day (default), week or month."
    • changedInput schema / properties / since / description
      Previous value: -"The date to start the analytics from (YYYY-MM-DD). Metric lag is an expected delay, not a strict cutoff; available data is returned through the requested date. Use social_platform_capabilities for channel-specific lag details."New value: +"First day of the range, YYYY-MM-DD, for example 2026-10-01."
    • changedInput schema / properties / until / description
      Previous value: -"The date to end the analytics at (YYYY-MM-DD). Metric lag is an expected delay, not a strict cutoff; available data is returned through the requested date. Use social_platform_capabilities for channel-specific lag details."New value: +"Last day of the range, YYYY-MM-DD, included. The last 1 to 3 days may not be available yet, depending on the channel; whatever data exists is returned."
    • changedOutput schema / properties / account_stats / items / properties / values / description
      Previous value: -"Available channel-specific metrics keyed by metric name for the selected period. Use social_platform_capabilities for full definitions and aggregation behavior."New value: +"Metrics for the period, keyed by metric name. The metrics differ by channel."
  2. Changed3 schema fields changed
    • changedOutput schema / properties / action_required / description
      Previous value: -"Present only when a user action is required before this request can be answered. The data block is empty and no credits were charged. Do not re-call this tool with different arguments or a wider date range; the workspace needs a change first, unless the action says how to adjust the call."New value: +"Present only when a user action is required before this request can be answered. The data block is empty and no credits were charged. Do not re-call this tool with different arguments or a wider date range; the workspace needs a change first, unless the action says how to adjust the call or names a tool that makes the change."
    • changedOutput schema / properties / action_required / properties / action / description
      Previous value: -"The action the user must take before this data becomes available."New value: +"The action that unblocks this request. When it names a tool, call that tool from the conversation; otherwise the user takes it in Sociality."
    • changedOutput schema / properties / action_required / properties / link / description
      Previous value: -"Sociality URL where the user takes that action."New value: +"Sociality URL where the user takes that action themselves."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add operational context — and it does: results are one row per period, metric names vary by channel, and recent data may lag. That channel-dependent metric naming is genuinely useful and is the strongest addition beyond structured fields; the data-lag note largely restates the 'until' parameter description.

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 usage trigger and scope are front-loaded, and the closing sentence efficiently hands off two sibling tools. It is slightly dense in the opening sentence's metric enumeration, but nothing is redundant enough to remove.

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?

An output schema exists so return values need no explanation, annotations carry the safety profile, and the description still supplies trigger, prerequisite, granularity, and routing. For a four-parameter read tool, an agent has everything needed to select and invoke it correctly.

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%, so since/until/period/account_id are all documented in the schema itself, which sets the baseline at 3. The description reinforces the period granularity ('per day, week or month') and the account-ID source, but adds no format or edge-case detail beyond what the schema already says.

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 and resource (retrieve account-level performance stats) plus the scope: the user's own accounts, over a date range, broken down per day/week/month. It enumerates the metric families (followers, growth, views, reach, likes, comments, shares) and explicitly distinguishes itself from the post-level and competitor siblings, so an agent can route without opening another schema.

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?

Gives an explicit trigger ('when the user asks how one of their own accounts performed over a date range') and names two alternatives with the conditions that select them: social_account_posts_list for single posts or per-post engagement rate, social_competitor_stats_list for competitors. It also states the prerequisite that the account ID must come from social_accounts_list.

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.