Skip to main content
Glama

Get Stream Feed

get_stream_feed
Read-onlyIdempotent

[Read · free] Return the most recent posts a stream has collected into the library, newest first by published_at. Use this to browse what a topic / external profile / person_interests / company stream has surfaced on its schedule.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stream_id": "<stream_id>"
    },
    "name": "get_stream_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax posts to return
stream_idYesStream ID from list_streams

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: the '[Read · free]' cost tag (no credit consumption) and the deterministic newest-first published_at ordering. It says nothing about truncation behavior at the limit, or what happens when the stream has collected no posts yet.

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 plus a bracketed cost tag, with the resource and ordering front-loaded and no filler. The cost tag earns its place; the stream-type enumeration is slightly listy but still informative rather than wasteful.

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 only two flat parameters, rich annotations, and no output schema, the definition covers what an agent needs to decide and call: what it returns, ordering, cost, and which stream types it serves. It stops short of describing the returned post fields, which matters somewhat because there is no output schema to fall back on.

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%, so both parameters are already documented in the schema ('Stream ID from list_streams', 'Max posts to return'), setting a baseline of 3. The description adds only indirect meaning by enumerating stream kinds (topic / external profile / person_interests / company), which helps an agent understand what stream_id points at but does not explain limit semantics or paging beyond 50.

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 and resource ('Return the most recent posts a stream has collected') plus the ordering ('newest first by published_at'), which is enough to distinguish it from write siblings like create_stream or run_stream_now. It does not name or contrast with the closest read sibling, get_posts, so an agent must infer the boundary between 'posts in a stream' and generic post retrieval.

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?

'Use this to browse what a ... stream has surfaced on its schedule' gives a clear use context and implicitly ties the tool to streams the user already configured. There is no explicit when-not guidance, no mention that the stream must have run at least once, and no pointer to an alternative for ad-hoc/post-set retrieval.

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