SocialGPT

Follower growth history

get_follower_history

Read-only

Get audience growth over time — follower / following / media counts as a true per-platform time series over the trailing window_days (default 90, up to 365). This is the trend get_account_metrics flattens to a latest-only value, so use it to answer "is my audience growing?". Omit account_id to aggregate across all connected accounts, or pass one from list_accounts; optionally filter to a single platform. granularity buckets server-side ('daily' default, 'weekly', or 'raw' for every scrape).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`platform`	No	Optional platform filter — instagram, tiktok, or youtube (case-insensitive). Omit to span all connected platforms.
`account_id`	No	A connected account_id from list_accounts. Omit to aggregate across all your accounts.
`granularity`	No	Time-series bucketing: 'daily' (default), 'weekly', or 'raw' (every scrape).	daily
`window_days`	No	Trailing window in days (1–365, default 90; out-of-range values are clamped).

Output Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Present only when the requested account_id could not be resolved.
`series`	Yes	Per-platform typed time series.
`platform`	Yes
`platforms`	Yes
`account_id`	Yes	The account_id the caller passed (null = all accounts).
`granularity`	Yes
`window_days`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 24, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Output of `get_follower_history`. `reason`='account_not_found' appears\nonly when the requested account_id resolved to none of the caller's\naccounts."

addedOutput schema / properties

Added value: +{
+  "account_id": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "The account_id the caller passed (null = all accounts)."
+  },
+  "granularity": {
+    "enum": [
+      "daily",
+      "weekly",
+      "raw"
+    ],
+    "type": "string"
+  },
+  "platform": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "platforms": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "reason": {
+    "anyOf": [
+      {
+        "const": "account_not_found",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Present only when the requested account_id could not be resolved."
+  },
+  "series": {
+    "additionalProperties": {
+      "items": {
+        "additionalProperties": true,
+        "description": "One time-series point. Metric columns (views, like_count,\nfollower_count, ...) are carried as additional properties; `bucket` is\npresent only for 'daily'/'weekly' granularity.",
+        "properties": {
+          "bucket": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null,
+            "description": "Bucket label (ISO date or ISO year-week); absent for granularity='raw'."
+          },
+          "timestamp": {
+            "anyOf": [
+              {
+                "format": "date-time",
+                "type": "string"
+              },
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "default": null,
+            "description": "Snapshot time of this point."
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "description": "Per-platform typed time series.",
+    "type": "object"
+  },
+  "window_days": {
+    "type": "integer"
+  }
+}

addedOutput schema / required

Added value: +[
+  "account_id",
+  "platform",
+  "window_days",
+  "granularity",
+  "platforms",
+  "series"
+]

Changed4 schema fields changedJun 24, 2026

addedInput schema / properties / account_id / description

Added value: +"A connected account_id from list_accounts. Omit to aggregate across all your accounts."

addedInput schema / properties / granularity / description

Added value: +"Time-series bucketing: 'daily' (default), 'weekly', or 'raw' (every scrape)."

addedInput schema / properties / platform / description

Added value: +"Optional platform filter — instagram, tiktok, or youtube (case-insensitive). Omit to span all connected platforms."

addedInput schema / properties / window_days / description

Added value: +"Trailing window in days (1–365, default 90; out-of-range values are clamped)."

AddedJun 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds trailing window behavior, granularity options, and server-side bucketing. No contradictions.

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 sentences with no filler. Front-loaded with purpose and key constraints. Every sentence earns its place.

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?

For a tool with 4 optional params, output schema present, and good annotations, the description covers aggregation, filtering, bucketing, and window. Complete.

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

Parameters4/5

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

Schema coverage is 100%, but description adds meaning: default 90 days, up to 365, clamping, aggregation when omitted, 'raw' for every scrape. All parameters explained beyond 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 'get audience growth over time' with specific metrics (follower/following/media counts) and differentiates from sibling get_account_metrics by noting that it provides a time series while the other flattens to latest-only.

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?

Explicitly says 'use it to answer 'is my audience growing?'' and explains when to omit account_id or platform. Lacks explicit when-not-to-use or alternative tools beyond the one mentioned.

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

All SocialGPT tools Inspect

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.