Synoptic

List followed streams

streams_following

Read-only

List streams the signed-in account follows, with optional metadata filters and pagination. Use streams_created for streams you own, streams_all or search for the public catalog, and get_following_users for followed authors.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of streams in this page.
`sortBy`	No	FOLLOWERS sorts most-followed first, CREATED_AT newest first. When omitted, ACTIVE streams first (states sort alphabetically), then featured, then most-followed.
`nextToken`	No	nextToken from the previous page; keep the other filters and sortBy unchanged.
`streamType`	No	Only PUBLIC or only PRIVATE streams. PRIVATE streams are visible only to their owner and to users who follow, subscribe to, were invited to, or have organization access to them.
`pricingType`	No	FREE: no direct price and not package-only. PAID: sold as a direct subscription. PACKAGE_ONLY: sold only in stream packages. ALL or omitted: any pricing.
`streamState`	No	Only streams in this lifecycle state; DRAFT streams are not yet published. Omit for any state.
`streamCategory`	No	Only streams in this topic category. Omit for any category.

Output Schema

Name	Required	Description	Default
`items`	Yes
`nextToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / sortBy / enum

Previous value: -[
-  "FOLLOWERS",
-  "CREATED_AT"
-]New value: +[
+  "FEATURED",
+  "FOLLOWERS",
+  "CREATED_AT"
+]

Changed2 schema fields changedOct 18, 2026

changedInput schema / properties / sortBy / description

Previous value: -"FOLLOWERS sorts most-followed first, CREATED_AT newest first. When omitted, sorts by state, then featured streams first, then most-followed."New value: +"FOLLOWERS sorts most-followed first, CREATED_AT newest first. When omitted, ACTIVE streams first (states sort alphabetically), then featured, then most-followed."

changedInput schema / properties / streamType / description

Previous value: -"Only PUBLIC or only PRIVATE streams. PRIVATE streams are visible only to their owner and to invited, subscribed or organization users."New value: +"Only PUBLIC or only PRIVATE streams. PRIVATE streams are visible only to their owner and to users who follow, subscribe to, were invited to, or have organization access to them."

Changed7 schema fields changedOct 18, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of streams in this page."

addedInput schema / properties / nextToken / description

Added value: +"nextToken from the previous page; keep the other filters and sortBy unchanged."

addedInput schema / properties / pricingType / description

Added value: +"FREE: no direct price and not package-only. PAID: sold as a direct subscription. PACKAGE_ONLY: sold only in stream packages. ALL or omitted: any pricing."

addedInput schema / properties / sortBy / description

Added value: +"FOLLOWERS sorts most-followed first, CREATED_AT newest first. When omitted, sorts by state, then featured streams first, then most-followed."

addedInput schema / properties / streamCategory / description

Added value: +"Only streams in this topic category. Omit for any category."

addedInput schema / properties / streamState / description

Added value: +"Only streams in this lifecycle state; DRAFT streams are not yet published. Omit for any state."

addedInput schema / properties / streamType / description

Added value: +"Only PUBLIC or only PRIVATE streams. PRIVATE streams are visible only to their owner and to invited, subscribed or organization users."

First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, non-open-world behavior. The description adds useful context by scoping results to the signed-in account and mentioning pagination, though it does not elaborate on private-stream visibility or auth requirements beyond the 'signed-in' implication.

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, front-loaded with the core purpose and followed by sibling-routing guidance. Every phrase serves selection or disambiguation.

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?

Given full schema coverage, rich annotations, and an existing output schema, the description provides everything needed for correct selection and invocation. Return-value details are appropriately left to the output schema.

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 coverage is 100%, so all seven parameters are already documented in the input schema, including enums and defaults. The description only mentions optional metadata filters and pagination generically, adding no parameter-level meaning beyond the 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?

The description states a specific verb and resource: list streams followed by the signed-in account. It immediately distinguishes this tool from sibling tools by naming streams_created, streams_all, search, and get_following_users as alternatives for other scopes.

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?

It explicitly tells the agent when to use this tool and when to use alternatives: streams_created for owned streams, streams_all or search for the public catalog, and get_following_users for followed authors. This leaves little ambiguity about routing.

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

All Synoptic 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?