Skip to main content
Glama

mcp-server

by com.echosaw

echosaw_set_media_visibility

Idempotent

Toggle whether a media item is published to the Public Library. Requires the analysis to be COMPLETE and the caller to own the item (or be an org member). Public Library publishing is blocked when content moderation flags (profanity, hate speech, nudity, violence, etc.) are present — those flags are returned in the response so the caller can surface them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mediaIdYesThe mediaId to update. Use echosaw_list_media to find available mediaIds.
isPublicYestrue to publish to the Public Library, false to make the item private again.

TDQS

A4.5/5.0
Behavior5/5

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

Description adds significant behavioral context beyond annotations: conditions (COMPLETE analysis, ownership), moderation flag blocking, and that flags are returned in the response. This goes well beyond the readOnly/destructive/idempotent hints already provided.

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 main action, and every sentence adds necessary information without redundancy. 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?

For a simple toggle tool, the description covers the action, prerequisites, blocking conditions, and response content (flags). Combined with rich schema and annotations, this is fully sufficient for an agent to select and invoke 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?

Schema description coverage is 100%, so the schema already documents both mediaId and isPublic. The description adds no extra parameter-specific meaning, only general context about moderation flags, which is not directly tied to parameter semantics.

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 states the tool's purpose: 'Toggle whether a media item is published to the Public Library.' This uses a specific verb+resource combination and differentiates it from sibling tools, none of which handle visibility toggling.

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 provides explicit prerequisites: 'Requires the analysis to be COMPLETE and the caller to own the item (or be an org member).' It does not explicitly name alternatives, but sibling tools do not overlap with this functionality, so the guidance is clear and sufficient.

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

All mcp-server 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

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