mcp-server

echosaw_list_media

Read-onlyIdempotent

List media items in your Echosaw library with metadata including filename, type, status, size, duration, and Public Library visibility (isPublic). Returns up to 25 items by default. Use this to browse your media library or find a specific mediaId. Supports optional folder filtering and server-side filters for media type, job status, report sentiment, and Public Library visibility (isPublic).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of items to return (default: 25)
`status`	No	Filter by job status (e.g. "COMPLETE", "PROCESSING", "FAILED").
`isPublic`	No	Filter by Public Library visibility. true returns only items published to the Public Library; false returns only private items. Omit to return all items.
`mediaType`	No	Filter by media type. One of "VIDEO", "AUDIO", or "IMAGE" (case-insensitive).
`sentiment`	No	Filter by report sentiment. One of "positive", "negative", "neutral", or "mixed" (case-insensitive).
`folderPath`	No	Filter by folder path (e.g., "/Marketing"). Defaults to "/" (root, all items).

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral context: 'Returns up to 25 items by default' and lists server-side filters, which informs the agent about default limits and filtering capabilities. No contradiction with annotations.

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 two sentences, front-loaded with the core action and metadata. It efficiently covers purpose, default limit, use case, and filters without padding. Every sentence earns its place.

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?

For a list tool with 6 parameters and no output schema, the description is quite complete: it states the returned metadata fields, default limit, filters, and use case. It could mention pagination or the folderPath default, but the schema covers those details. Overall, sufficient for safe invocation.

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%, with each parameter adequately described (e.g., 'Filter by job status'). The description adds minimal extra meaning—just grouping 'server-side filters' collectively. Since the schema already documents all parameters, the description provides no significant additional semantics.

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?

The description clearly states the tool lists media items with metadata and mentions use cases ('browse your media library or find a specific mediaId'). It distinguishes from sibling echosaw_search_media by framing this as browsing rather than searching, but doesn't explicitly name or contrast alternatives, so it falls short of a 5.

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?

The description gives clear usage context ('Use this to browse your media library or find a specific mediaId'), which helps the agent decide when to invoke it. However, it does not mention when not to use it or explicitly point to alternatives like echosaw_search_media, so it lacks full exclusion guidance.

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

All mcp-server tools Inspect

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

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct action and resource: analysis jobs (submit, check, get results, download), folder management (create, delete, list, rename), media operations (list, move, search, set visibility), and account info (organization, profile). There is no overlap or ambiguity between tools.

Naming Consistency5/5

All tools follow the consistent pattern `echosaw_<verb>_<noun>`, using clear verbs like analyze, check, create, delete, get, list, move, rename, search, and set. The naming style is uniform and predictable across the entire set.

Tool Count5/5

With 14 tools, the server covers a well-scoped platform for media analysis and library management. Each tool serves a clear purpose without feeling bloated or sparse, fitting comfortably within the ideal range.

Completeness4/5

The server covers the full analysis workflow, folder organization, media searching, and account retrieval. Minor gaps exist such as lack of media deletion or job cancellation, but core workflows are well supported and no critical dead ends are apparent.

Resources

Need Help?