MightyAutomation

List media assets

list_media_assets

Read-onlyIdempotent

Files in the workspace Media Assets library, newest first — title, kind, MIME type, size, tags, and source. Metadata only (no download links). Use import_file to add a file.

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": "list_media_assets"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Only assets of this kind.
`limit`	No	Max assets, 1-200 (default 50).

Output Schema

Name	Required	Description
`ok`	No
`error`	No	Present only when ok is false.
`assets`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world semantics, so the bar is lower. The description still adds two useful facts beyond the annotations: result ordering (newest first) and that no download URLs are returned — both affect how an agent should consume the output.

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 tight sentences: the first front-loads what it returns and in what order, the second covers the key exclusion plus the write alternative. No filler.

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 two-optional-param read tool with an output schema and full annotation coverage, this is sufficient: ordering, return fields, the no-download caveat, and where to go to add files are all stated.

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% and both params (kind enum, limit 1-200 default 50) are fully documented there. The description adds nothing about the filter or pagination behavior, so baseline 3 applies.

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?

States the specific resource (Media Assets library in the workspace), the ordering (newest first), and the fields returned (title, kind, MIME type, size, tags, source). An agent can immediately tell this is a read/lookup tool for files, distinct from import_file which writes.

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?

Explicitly notes 'Metadata only (no download links)' which sets expectations, and redirects writes to import_file. It doesn't need to disambiguate from other list_* siblings since none overlap, but it also doesn't spell out when the kind filter should be preferred.

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

All MightyAutomation 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?