Skip to main content
Glama

Synoptic

by com.synoptic
OverviewDiscussionsAdmin

List my streams

streams_created
Read-only

List streams the signed-in account owns, including unpublished DRAFT streams, with optional filters and pagination. Use it to find IDs for create_stream_post, update_stream, publish_stream or delete_stream. Use streams_following for streams you follow, and search or streams_all for the public catalog.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the result set is ownership-scoped and includes unpublished DRAFT streams, which is a meaningful difference from public listings. It does not add detail on pagination mechanics, but the schema covers those.

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?

Three sentences, zero waste, and the critical scoping fact (owner-only, includes DRAFTs) is front-loaded before the routing guidance. Each sentence earns its place.

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?

An output schema exists, so return values need no explanation, and the description covers ownership scope, the draft-inclusion behavior, and how to route to sibling read tools. Nothing an agent needs to invoke a no-required-parameter list tool correctly is missing.

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% and five of seven parameters carry detailed enum documentation, so the schema does the heavy lifting. The description only says 'optional filters and pagination' generically and adds no filter syntax or semantics beyond what is already documented.

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 precise verb and resource ('List streams the signed-in account owns') and adds the distinguishing scope detail that unpublished DRAFT streams are included. It explicitly separates itself from streams_following, streams_all, and search, so an agent can pick it 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?

Gives explicit downstream uses ('find IDs for create_stream_post, update_stream, publish_stream or delete_stream') and names the alternatives with the condition that selects them ('streams_following for streams you follow', 'search or streams_all for the public catalog'). Nothing is left to inference.

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