StreamClipping AI

Publishing analytics

get_analytics

Read-only

Views, likes and top posts over a period, per platform. Only covers posts published from StreamClipping AI.

Input Schema

Name	Required	Description	Default
`creator`	No	Agency creator to scope to, by name or id (see the creator profiles of the account). 'default' targets the default profile, the one without a named creator. Omit to cover all creators of the organization.
`periodDays`	No	Analysis window, in days.

Output Schema

Name	Required	Description
`note`	Yes	Reading note, in particular when no data is available.
`topPosts`	Yes
`byPlatform`	Yes
`periodDays`	Yes
`totalLikes`	Yes
`totalViews`	Yes
`publishedPosts`	Yes
`avgViewsPerPost`	Yes
`youtubeByChannel`	Yes	YouTube views channel by channel, clips published in the last 28 days at most. Never added to the other networks nor across channels.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

addedOutput schema / properties / youtubeByChannel

Added value: +{
+  "description": "YouTube views channel by channel, clips published in the last 28 days at most. Never added to the other networks nor across channels.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "channel": {
+        "description": "UNTRUSTED TEXT: YouTube channel name.",
+        "type": "string"
+      },
+      "posts": {
+        "type": "number"
+      },
+      "views": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "channel",
+      "views",
+      "posts"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "periodDays",
-  "publishedPosts",
-  "totalViews",
-  "totalLikes",
-  "avgViewsPerPost",
-  "byPlatform",
-  "topPosts",
-  "note"
-]New value: +[
+  "periodDays",
+  "publishedPosts",
+  "totalViews",
+  "totalLikes",
+  "avgViewsPerPost",
+  "byPlatform",
+  "topPosts",
+  "youtubeByChannel",
+  "note"
+]

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / creator

Added value: +{
+  "description": "Agency creator to scope to, by name or id (see the creator profiles of the account). 'default' targets the default profile, the one without a named creator. Omit to cover all creators of the organization.",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

First observedOct 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a safe, closed-world read (readOnlyHint true, destructiveHint false, openWorldHint false). The description adds genuinely non-obvious behavioral context beyond them: the dataset is limited to posts published from StreamClipping AI, which tells the agent results may under-report versus native platform analytics. It does not mention any auth or permission requirements, but for a read-only tool with annotations covering the safety profile this is a modest gap.

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 short sentences, zero filler, with the content of the report front-loaded and the important coverage caveat placed as a separate scoping sentence.

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?

An output schema exists, so the description needn't explain return shape, and the schema documents both parameters thoroughly. The only meaningful gap is the absence of any note on how per-platform figures are aggregated or what happens when no data exists in the window, which is minor for a two-parameter read tool.

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 the creator scoping rules and the 7/30/90-day window are already fully documented in the schema. The description reinforces the period concept ("over a period") and hints at a per-platform breakdown, but adds no syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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?

The description names the concrete metrics returned (views, likes, top posts), the grouping dimension (per platform) and the analysis window, so an agent knows exactly what this tool produces. It is clearly the only analytics/reporting tool among the siblings, though the verb is implicit ("Views, likes and top posts") rather than an explicit "retrieve".

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?

There is no explicit when-to-use statement or comparison to a sibling, and no alternative analytics tool exists to route to. The scope restriction ("Only covers posts published from StreamClipping AI") functions as an implicit when-not condition, which is useful but is the only usage guidance present.

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

All StreamClipping AI 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.

Resources

Need Help?