Skip to main content
Glama

List Streams

list_streams
Read-onlyIdempotent

[Read · free] List all research streams for the authenticated user (external profiles, companies, topics, person interests, hiring signals, ad watches, and own_profile). Pass type to filter. Replaces list_profiles for the streams-first world, but list_profiles continues to work for V1-compatible callers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_streams"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by stream type
include_inactiveNoInclude paused streams (active = false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond them: the '[Read · free]' tag signals no credit cost (relevant given a credit-balance sibling exists) and the authenticated-user scope clarifies whose streams are returned. It says nothing about result size, pagination, or ordering of the returned list.

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 tight sentences with the read/free marker and the core listing scope front-loaded, followed by the parameter hint and the sibling disambiguation. The enumeration of stream types is somewhat redundant with the enum in the schema, but it is compact and aids scanning.

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?

For a zero-required-parameter list tool with no output schema, the definition gives enough to invoke it correctly: scope, filter parameter, and the sibling relationship. It could say more about what a stream object contains or whether inactive streams are omitted by default, but the schema default and annotations cover the essentials.

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 both parameters are already documented, including the enum values and the include_inactive default. The description only restates the `type` filter and its allowed values, which largely duplicates the schema, and never mentions include_inactive or the paused-stream concept. Baseline 3 is appropriate since the schema does the heavy lifting.

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 opens with a specific verb and resource ('List all research streams'), scopes it to 'the authenticated user', and enumerates the concrete stream kinds (external profiles, companies, topics, person interests, hiring signals, ad watches, own_profile). It explicitly distinguishes itself from the sibling list_profiles, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names list_profiles as the alternative and gives the condition for choosing this one ('streams-first world' vs 'V1-compatible callers'), plus the instruction to pass `type` when filtering. What's missing is guidance on when not to filter, or on choosing between this and other list_* siblings such as list_collections or list_segments.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources