StreamClipping AI

List clips

list_clips

Read-only

Clips of the account or of one project, sorted by estimated viral potential by default. Titles and hooks come from what was said on stream.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No	Cursor returned by a previous call.
`sortBy`	No	Sort order. 'views' ranks by cumulative views of the posts.	viralityScore
`status`	No	Filter by status. READY means publishable clips.
`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.
`projectId`	No	Limit to one project. Omit to scan all clips.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`clips`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description usefully adds the default sort (viral potential) and the source of titles/hooks, but says nothing about pagination/cursor limits or result volume beyond what the schema provides.

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?

Two sentences, front-loaded with scope and default ordering, with no filler. The second sentence about titles/hooks earns its place by explaining where those fields originate.

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 return values need not be described, and annotations cover the safety profile. Scope and default ordering are stated; the definition is adequate for a low-risk, zero-required-parameter listing 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 high (83%) with self-documenting descriptions for cursor, sortBy, status, creator and projectId, so the structured data carries the load. The description's mention of 'account or of one project' and default sort largely restates the schema rather than adding syntax or edge-case meaning.

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?

States a specific verb+resource ('Clips of the account or of one project') plus the default sort behavior, making the scope clear. It does not explicitly distinguish itself from the singular sibling get_clip, relying on the plural to imply listing.

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 by the listing nature of the tool; there is no explicit when-to-use guidance or reference to alternatives such as get_clip for a single clip or list_projects for project scoping. An agent can infer its role but is given no routing rules.

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?