Skip to main content
Glama
speakai

Speak AI MCP Server

Official
by speakai

List Media Files

list_media
Read-onlyIdempotent

List and search media files with filters for type, name, folder, date range, and favorites. Include transcripts, speakers, or keywords inline to avoid extra API calls.

Instructions

List and search media files in the workspace with filtering, pagination, and sorting. Use filterName for text search, mediaType to filter by audio/video/text, folderId for folder-specific results, and from/to for date ranges. Use the include param to embed additional data (transcripts, speakers, keywords) inline with each result, avoiding N+1 API calls. Returns mediaIds you can pass to get_transcript, get_media_insights, or ask_magic_prompt. For deep full-text search across transcripts, use search_media instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date for date range filter (ISO 8601)
fromNoStart date for date range filter (ISO 8601)
pageNoPage number for pagination (0-based, default: 0)
sortByNoSort field and direction, e.g. "createdAt:desc" or "name:asc"
includeNoAdditional data to include with each media item. Without this, only metadata is returned. Use 'transcription' to include full transcripts inline, 'speakers' for speaker details, 'keywords' for extracted keywords, etc. Avoids N+1 API calls when you need data for multiple files.
folderIdNoFilter media within a specific folder
pageSizeNoNumber of results per page (default: 20, max: 500)
mediaTypeNoFilter by media type: "audio", "video", or "text"
filterNameNoFilter media by partial name match
filterMediaNoFilter: 0=Uploaded, 1=Assigned, 2=Both (default: 2)
isFavoritesNoFilter to only show favorited media

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoResponse payload from the Speak AI API
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint. Description adds value by explaining include param's benefit for avoiding N+1 calls and what additional data can be embedded. No contradictions.

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?

Four sentences, each adding unique value: purpose, param highlights, include benefit, cross-tool usage. No redundant or wasted text.

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?

Despite 11 params, description covers filtering, pagination, sorting, the critical include param, and ties to other tools. Output schema exists so return values are covered. Highly complete for a list tool.

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?

Schema coverage is 100%, so baseline is 3. Description reinforces key params (filterName, mediaType, folderId, from/to, include) and explains include's purpose beyond schema, justifying a 4.

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?

Description clearly states 'List and search media files' with specific capabilities (filtering, pagination, sorting). Distinguishes from sibling search_media by noting 'For deep full-text search across transcripts, use search_media instead.'

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 says when to use this tool vs search_media, advises use of include param to avoid N+1 calls, and mentions downstream tools for returned mediaIds.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/speakai/speakai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server