Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List media

list_media
Read-only

List media files and images in a Cmssy workspace, newest first, with cursor or offset pagination to browse large libraries page by page.

Instructions

List media files (images and files) in the workspace, newest first. Paginated: while hasMore is true, pass nextCursor back as cursor while it is set; if hasMore is true but nextCursor is null, page with the offset instead, and past offset 10000 narrow the filter.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNonextCursor from the previous page. The page continues after it in the same filter and sort; leave the skip/offset at 0 when you pass it
offsetNoHow many rows to skip, at most 10000; page past that with cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.146.2
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "nextCursor from the previous page. The page continues after it in the same filter and sort; leave the skip/offset at 0 when you pass it",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / offset / description
      Added value: +"How many rows to skip, at most 10000; page past that with cursor"
    • changedInput schema / properties / offset / maximum
      Previous value: -9007199254740991New value: +10000
    • changedInput schema / properties / offset / minimum
      Previous value: --9007199254740991New value: +0
  2. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / default
      Removed value: -50
    • removedInput schema / properties / offset / default
      Removed value: -0
  3. First observedv0.73.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds genuinely new behavior: sort order, the hasMore/nextCursor loop, the degenerate hasMore=true-but-null-cursor case, and the 10000 offset ceiling with the narrowing-filter remedy.

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 purpose and sort order, then a single dense pagination sentence. The conditional chain ('while hasMore is true ... if hasMore is true but nextCursor is null ...') is necessarily compound but slightly hard to parse in one pass; nothing is wasted.

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 correctly enumerates the response-side fields the agent must branch on (hasMore, nextCursor) and gives complete instructions for every pagination state. For a read-only list tool with three simple parameters, an agent can call and iterate it correctly from this text alone.

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 67%, with cursor and offset already documented in the schema; limit is undocumented in both places. The description supplies the missing relational semantics — that nextCursor is fed back as cursor in the same filter and sort, and that offset is capped and should be replaced by cursor/filter narrowing — which is real added value, though it never explains what limit controls or its default.

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 a specific verb and resource ('List media files (images and files)') plus scope ('in the workspace') and sort order ('newest first'), so the agent knows exactly what comes back. It does not explicitly distinguish itself from near siblings like list_trashed_media or list_media_folders, leaving the workspace-vs-trashed boundary implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives strong procedural guidance for pagination (when hasMore is true, pass nextCursor; fall back to offset; narrow the filter past 10000), but nothing about when to choose this tool over list_trashed_media or a folder-scoped listing. Usage is implied by scope rather than stated.

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

Deploy Server

Other Tools