Skip to main content
Glama

Storyflo

by io.github.Alisammour

My storyflo status

publisher_status
Read-onlyIdempotent

Where a publisher stands right now: their RSS feed URL (the one to submit to Apple Podcasts and Spotify), how many episodes storyflo holds, how many already have finished audio, and how many are still awaiting source audio. Use this for 'what is my feed URL', 'is anything stuck', or as the first call when a publisher asks how things are going.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesYour publisher access token — the same one the dashboard uses. Rotatable at POST /v1/publisher/{slug}/access-token/rotate.
tenant_slugYesYour publisher slug on storyflo.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds useful domain context, such as the feed URL being the one to submit to Apple Podcasts and Spotify, and clarifies what the episode counts mean, going beyond the structured annotation data.

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 a single, information-dense sentence followed by concrete usage examples. Every word adds value and there is no redundancy or filler.

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 no output schema, the description adequately enumerates the key return values (feed URL, episode counts, audio state). It could mention edge cases like zero episodes or error conditions, but for the tool's simple scope it is sufficiently 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%, and the schema already thoroughly explains both token and tenant_slug. The description adds no additional parameter-specific information, so a baseline score of 3 is appropriate.

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 clearly defines the tool as a status overview showing a publisher's feed URL, episode counts, and audio status. It differentiates itself from sibling tools by being the 'first call' status check, as opposed to detailed episode or stats tools.

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?

Concrete example queries ('what is my feed URL', 'is anything stuck') and a recommendation to use it as the first call provide clear usage context. However, it does not explicitly mention when not to use it or name alternative tools for specific needs.

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