StreamClipping AI

StreamClipping AI account status

get_account

Read-only

Current plan, available processing minutes, remaining magic clipping quota and connected social accounts. An import fails when minutes run short. During the free trial, the quota is one hour of video PER DAY, refilled at midnight local time (trialDaily field).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	Yes	Effective plan: FREE, CREATOR, PRO or ELITE. During the trial, this is the trial plan.
`trial`	Yes	Current trial. `active` is false when the organization is not on a trial.
`appUrl`	Yes	Web app address, for actions that are handled there.
`minutes`	Yes	Minutes wallet. One minute is consumed per minute of source video processed, not per clip produced.
`paidPlan`	Yes	Plan on the account, trial excluded. A gifted ambassador plan also appears here; whether X publishing is allowed is given by canPublishHere in list_social_accounts.
`retestPass`	Yes	Two-video pass: a one-time purchase that gives back the trial features for 2 new videos (up to 1 hour each), no live. Not a trial and not a subscription: nothing is charged when it ends.
`trialDaily`	Yes	Free trial only: one hour of video per day, not cumulative, refilled at midnight local time. null outside the free trial. When the day's minutes run out, the options are waiting for the refill or moving to a paid plan.
`magicClipping`	Yes	Magic clipping: fully automatic detection and editing.
`socialAccounts`	Yes	Connected social accounts. Publishing requires an ACTIVE account. TWITCH is only used for importing, never for publishing. Publishing on X (TWITTER) requires a paid Pro or Elite plan.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedOutput schema / properties / retestPass

Added value: +{
+  "additionalProperties": false,
+  "description": "Two-video pass: a one-time purchase that gives back the trial features for 2 new videos (up to 1 hour each), no live. Not a trial and not a subscription: nothing is charged when it ends.",
+  "properties": {
+    "active": {
+      "type": "boolean"
+    },
+    "daysLeft": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "active",
+    "daysLeft"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "plan",
-  "paidPlan",
-  "trial",
-  "minutes",
-  "trialDaily",
-  "magicClipping",
-  "socialAccounts",
-  "appUrl"
-]New value: +[
+  "plan",
+  "paidPlan",
+  "trial",
+  "retestPass",
+  "minutes",
+  "trialDaily",
+  "magicClipping",
+  "socialAccounts",
+  "appUrl"
+]

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 establish a safe, closed-world read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lowered, and the description still adds real behavior: imports fail when minutes run short, and the trial quota is one hour of video per day refilled at midnight local time surfaced in the trialDaily field. That is meaningful operational context beyond the structured data.

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?

Three sentences, front-loaded with the returned field list and then the quota mechanics. Every sentence carries information; nothing is padding, though the phrasing is slightly list-like rather than tightly organized around a single intent.

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?

With an output schema present the description is not obliged to explain return values, yet it usefully characterizes them plus the quota-refill rule and the consequence of exhaustion. For a no-parameter, read-only status tool this is essentially complete; only the relationship to get_analytics is unaddressed.

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?

The tool takes zero parameters, so the baseline of 4 applies and schema coverage is moot. The description correctly spends no space on inputs.

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 resource (the account) and enumerates exactly what is returned: plan, processing minutes, magic clipping quota, connected social accounts. That is far more specific than the title. It stops short of distinguishing itself from the adjacent sibling get_analytics, which an agent could plausibly confuse with quota/usage reporting.

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?

Usage is only implied: the note that 'an import fails when minutes run short' hints that this tool should be consulted before/after import_vod, but it never states when to call it or how it differs from get_analytics. No explicit when-to-use or when-not-to-use guidance is given.

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?