Skip to main content
Glama

Synoptic

by com.synoptic
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of streams in this page.
sortByNoFOLLOWERS sorts most-followed first, CREATED_AT newest first. When omitted, ACTIVE streams first (states sort alphabetically), then featured, then most-followed.
nextTokenNonextToken from the previous page; keep the other filters and sortBy unchanged.
streamTypeNoOnly 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.
pricingTypeNoFREE: 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.
streamStateNoOnly streams in this lifecycle state; DRAFT streams are not yet published. Omit for any state.
streamCategoryNoOnly streams in this topic category. Omit for any category.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
nextTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
  2. Changed7 schema fields changed
    • 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."
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds that filters are optional and results are paginated, and implies an authenticated 'signed-in' context, but says nothing about page-size limits or rate behavior. With annotations carrying the safety burden, this is adequate but thin.

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, zero filler. The what is front-loaded and the routing guidance follows immediately, so an agent gets purpose and disambiguation in one pass.

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, return values need no explanation, and the rich schema covers filtering. What remains slightly under-addressed is behavioral context around pagination (page cap of 50 is only in the schema) and the effect of combining filters, but for a read-only list tool the description is effectively complete.

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% with 7 documented parameters and 5 enums, so the schema does all the semantic work (including the non-obvious default sort ordering). The description only says 'optional metadata filters and pagination,' adding no meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource with scope: 'List streams the signed-in account follows.' The scope ('the signed-in account follows') is exactly what separates it from the catalog-listing siblings, so an agent can disambiguate without opening a schema.

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 routes to alternatives with the condition that selects each: streams_created for owned streams, streams_all/search for the public catalog, get_following_users for followed authors. This is a complete when-to-use map rather than a hint.

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

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