Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

get_follower_growth

Track follower and subscriber growth across connected social accounts over selected time windows, with current counts, change, and percent change from daily captures.

Instructions

Follower/subscriber growth per connected account over a time window: current count, change and percent change. Counts are captured once a day; LinkedIn and TikTok accounts cannot report followers.

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

Input Schema

NameRequiredDescriptionDefault
periodNoTime window (default: last 30 days)
platformNoOnly accounts on this platform (e.g. "x")
connectionNoOnly this account, by connection slug (e.g. "instagram-mybrand")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that counts are captured once a day (so intra-day refreshes are pointless and last_day data may be stale) and states a platform-level data availability limitation. It omits empty/missing-account return behavior, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: return shape first, then cadence and availability constraints. No filler, and the most decision-relevant constraint (daily capture) is placed early.

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?

For a 3-parameter read tool with no output schema, it sufficiently describes return contents, data freshness, and platform gaps. Only minor gaps remain, such as behavior when a connection has no follower data at all.

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 period, platform, and connection are already documented with examples and the enum. The description only restates the concept of a time window and adds no format or interaction detail beyond the schema, making 3 the correct baseline.

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?

Names a specific metric (follower/subscriber growth) at a specific granularity (per connected account, over a time window) and enumerates the returned values (current count, change, percent change). This clearly separates it from get_post_analytics, get_usage, and compare_accounts, though no sibling is named 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?

Provides a useful exclusion: LinkedIn and TikTok accounts cannot report followers, which steers an agent away from fruitless calls. However, there is no positive when-to-use guidance and no routing to compare_accounts for cross-account comparison, leaving the choice implicit.

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