Skip to main content
Glama

Storyflo

by io.github.Alisammour

Subscribe to topic feed

subscribe_topic
Idempotent

Mint or update the human's personal Storyflo podcast feed. Pass 1–6 vertical slugs from tech, finance, science, media, sports, culture. The server creates a private RSS feed scoped to those verticals — or updates the existing feed in place if the listener already has one. Returns the RSS URL the listener can paste into Spotify, Apple Podcasts, Pocket Casts, or any podcast client.

Behavior • Persistent server-side side-effect — a ListenerSubscription row is created or updated. The returned RSS URL stays stable across calls for the same listener (the listener doesn't need to re-paste it). • Idempotent on identical input — calling twice with the same verticals leaves state unchanged. • REPLACES on different input — calling with a different verticals set OVERWRITES the previous selection rather than adding to it. Use this to switch a listener's feed; do NOT call to add verticals incrementally (read the current set via list_subscriptions first and pass the union if you want additive behavior). • Single feed per listener — call list_subscriptions first to avoid clobbering an existing feed the listener explicitly chose.

When to use Use after the agent has been asked to set up audio news for the human across a defined set of topics. Do NOT use to FETCH articles or audio — that's search_articles + get_audio_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
verticalsYes1–6 vertical slugs the feed should cover. Replaces (not appends) the listener's current selection.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already include idempotentHint and destructiveHint, but the description adds crucial side-effect details: persistent server-side write, idempotency on identical input, full replacement on different input, and stability of the RSS URL. This goes well beyond the structured fields and fully explains behavior.

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?

The description is well-structured with clear sections ('Behavior', 'When to use') and every sentence adds useful information. It is appropriately concise for a tool with side-effect behavior, and the first sentence front-loads the core purpose.

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?

The tool has a single parameter, no output schema, and rich behavioral guidance. The description covers when to use, what happens on re-invocation, how to avoid pitfalls, and what the return value is (RSS URL). It is fully sufficient for an agent to select and invoke the tool correctly.

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?

The schema provides 100% coverage of the single parameter, including a description ('Replaces (not appends) the listener's current selection.') and enum values. The tool description repeats the valid slugs and the 1–6 constraint but doesn't add new semantics beyond what the schema already states.

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 ('Mint or update') and resource ('the human's personal Storyflo podcast feed'), making it immediately clear what the tool does. It also distinguishes itself by naming alternatives: 'Do NOT use to FETCH articles or audio — that's search_articles + get_audio_url.'

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?

A dedicated 'When to use' section explicitly states when to use the tool ('Use after the agent has been asked to set up audio news...') and what not to use it for. It also instructs to call `list_subscriptions` first to avoid clobbering an existing feed, giving clear contextual guidance.

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

All Storyflo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Even similar tools like search_articles, search_declassified, and search_unified target different corpora, and the publisher tools are well-separated. No overlap that would confuse an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, using clear prefixes like get_, search_, subscribe_, publisher_, fm_, digest_, etc. The naming is predictable and systematic, making it easy for an agent to infer functionality.

Tool Count4/5

At 37 tools, the count is higher than the typical 3-15 range for a coherent set, but the server covers a wide domain (content retrieval, podcast management, fund manager book, embedder network, etc.). Each tool earns its place, though the set could be slightly reduced by merging some rare-use tools.

Completeness4/5

The tool surface is comprehensive for the server's purpose—search, audio, subscriptions, publisher workflows, and special features like the Divergence Index. Minor gaps exist (e.g., no explicit unsubscribe tool, no article update/delete), but they are not critical for core workflows.

Resources