Skip to main content
Glama

Storyflo

by io.github.Alisammour

Connect a recordings folder

publisher_connect_folder
Idempotent

Connect a Google Drive folder of recordings so storyflo can match them to episodes automatically — the alternative to uploading a back catalogue file by file. Call with NO folder argument first to get the setup instructions, including the address to share the folder with. Then call again with folder=. Recording the connection moves no audio; the scan happens afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesYour publisher access token.
folderNoGoogle Drive folder URL or id. Omit to get setup instructions.
tenant_slugYesYour publisher slug on storyflo.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description reveals that recording the connection does not move audio and that scanning happens afterward. This explains the tool's side effects and operational model, adding valuable context that annotations alone don't provide.

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?

Two dense sentences cover purpose, usage, and behavior. No wasted words.

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?

Given the tool's simplicity and the annotations covering safety traits, the description explains the two-step process, the non-destructive nature, and the subsequent scan, making it sufficient for an agent to execute correctly without output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema already describes each parameter, the description adds crucial usage semantics for the 'folder' parameter: the two-phase invocation pattern ('Call with NO folder argument first... Then call again with folder=...'). It clarifies that the folder is a Drive URL and that omitting it yields setup instructions, going beyond the schema's brief description.

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 ('Connect') and resource ('Google Drive folder of recordings'), and clarifies the intended outcome ('match them to episodes automatically'). It also positions itself in contrast to uploading, which distinguishes it from sibling tools like publisher_upload_audio.

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?

Explicitly states it's the alternative to uploading a back catalogue file by file, giving a clear when-to-use. Provides step-by-step instructions: first call without folder argument gets setup instructions, then call with folder URL. This leaves no ambiguity about invocation sequence.

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