Feedlio

Look at media files

view_media

Read-onlyIdempotent

Show small previews of files in the media library so you can see them, e.g. to pick the right images for a post or put carousel images in a good order. Pass media_uids (from list_media, up to 6), or omit them to see the most recent images. Videos are shown as their thumbnail frame. Returns one image per file plus a short text list with each file's uid, name, type and size; files that can't be shown are listed with the reason. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "view_media"
  }
}

Input Schema

Name	Required	Description	Default
`media_uids`	No	Up to 6 uids from list_media; omit for the latest images
`workspace_uid`	No	uid from list_workspaces; omit for the default workspace

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds real behavioral detail beyond them: the hard cap of 6 uids, the default of latest images when omitted, video handling ('shown as their thumbnail frame'), and failure behavior ('files that can't be shown are listed with the reason'). These are material for an agent predicting what comes back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then the input options, then the return shape — a sensible order with no filler. It is dense and runs long as a single block, so the return-format and video/error details could be broken out for faster scanning.

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?

There is no output schema, so the description carries the return-value burden and does so: one image per file plus a text list with uid, name, type and size, plus the reason for unrenderable files. Combined with the default behavior and zero required parameters, an agent has everything needed to invoke and interpret this tool.

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 coverage is 100%, so both parameters are already documented, and the description's media_uids guidance ('from list_media, up to 6... omit for latest') largely restates the schema text. workspace_uid is not mentioned at all in the description, and no additional syntax or edge-case meaning is added, so baseline 3 applies.

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?

States a specific verb and resource ('Show small previews of files in the media library') and immediately frames the agent-facing intent ('so you can see them... pick the right images for a post'). This distinguishes it from list_media, which supplies the uids but returns metadata rather than visual previews.

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?

Gives clear triggering scenarios (choosing images for a post, ordering carousel images) and explains the two modes: pass media_uids from list_media, or omit for the most recent images. It lacks an explicit when-not or a direct 'use list_media for metadata instead' statement, which keeps it shy of a 5.

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

All Feedlio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?