SocialGPT

Growth summary

get_growth_summary

Read-only

Get a computed momentum summary for owned content over the trailing window_days (default 90). For each platform returns, per metric, the start/current value, absolute + percent change over the window, and a momentum read (recent half vs. prior half — accelerating). Audience metrics (follower/following/media counts) come from the true growth series; engagement metrics (views/likes/comments/shares) from recent-post activity. Higher-altitude than the raw series — use it to lead a performance audit, then drill in with get_follower_history / get_account_metrics.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`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.
`summary`	Yes	Per-platform, per-metric window summaries.
`platform`	Yes
`platforms`	Yes
`account_id`	Yes	The account_id the caller passed (null = all accounts).
`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_growth_summary`. `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)."
+  },
+  "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."
+  },
+  "summary": {
+    "additionalProperties": {
+      "additionalProperties": {
+        "description": "Window summary for one metric (see `get_growth_summary`).",
+        "properties": {
+          "accelerating": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "True when the recent half moved more than the prior half."
+          },
+          "change": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "number"
+              }
+            ]
+          },
+          "current": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "number"
+              }
+            ]
+          },
+          "pct_change": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Percent change start→current; null when start is 0."
+          },
+          "prior_change": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Change over the prior half of the window."
+          },
+          "recent_change": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Change over the recent half of the window."
+          },
+          "start": {
+            "anyOf": [
+              {
+                "type": "integer"
+              },
+              {
+                "type": "number"
+              }
+            ]
+          }
+        },
+        "required": [
+          "start",
+          "current",
+          "change",
+          "pct_change",
+          "recent_change",
+          "prior_change",
+          "accelerating"
+        ],
+        "type": "object"
+      },
+      "type": "object"
+    },
+    "description": "Per-platform, per-metric window summaries.",
+    "type": "object"
+  },
+  "window_days": {
+    "type": "integer"
+  }
+}

addedOutput schema / required

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

Changed3 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 / 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.6/5.0

Behavior4/5

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

Discloses computational behavior: returns start/current values, absolute+percent change, momentum read ('accelerating'). Explains data source differentiation. Annotations already provide readOnlyHint=true; description adds meaningful context without contradiction.

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 front-loaded purpose, detailed breakdown, and usage guidance. Every clause adds value, no redundancy or filler.

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?

Covers purpose, data sources, usage flow, and parameter defaults. Output schema exists so return values need not be elaborated. Slightly missing mention of error cases or prerequisite (e.g., accounts must exist), but sufficient given complexity.

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%, baseline 3. Description adds value by explaining defaults (window_days=90), platform filter case-insensitivity, account_id sourced from list_accounts, and clamping behavior. Goes beyond bare schema descriptions.

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?

Description uses specific verb 'get' and resource 'computed momentum summary', clearly defining the tool's output. It distinguishes itself from sibling tools (get_follower_history, get_account_metrics) by noting it's higher-altitude and for leading audits.

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?

Explicitly states when to use ('lead a performance audit') and suggests when to drill in with alternatives. Provides context on data sources (true growth series vs recent-post activity) to guide appropriate usage.

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.