Skip to main content
Glama
Sign In

Antwork

by io.antwork
OverviewDiscussionsAdmin

list_media

Read-only

The workspace media library: images, videos and PDFs, with URLs to attach.

libraryUrl is the library page in the web app. nextCursor, when not null, is passed back as cursor for the next page.

Args: media_type: "image", "video", "document" (PDFs), or omitted for all. limit: Max items per page (default 30, max 100). workspace_id: Workspace ID or name. Optional if user has only one workspace. cursor: nextCursor from the previous page.

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
cursorNo
contextNoThe user's underlying goal for this call, in one sentence without personal details. Used for product analytics only.
llm_modelNoThe model identifier of the calling assistant, or "unknown". Used for product analytics only.
media_typeNo
workspace_idNo
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "context",
-  "llm_model"
-]New value: +[]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), and the description goes beyond them by disclosing pagination mechanics ('nextCursor, when not null, is passed back as cursor'), the library page URL, and the single-workspace fallback for workspace_id. It stops short of stating ordering, total counts, or whether resources are filtered by permissions.

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 resource definition, then the response fields an agent needs for pagination, then a compact Args block. Every line earns its place; only minor redundancy between the prose and the Args list.

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?

Given an output schema exists, the description need not enumerate return fields, yet it usefully calls out libraryUrl and nextCursor. It omits result ordering and whether media is scoped to workspace permissions, which are the only remaining gaps for a 7-param read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 43%, but the description compensates by supplying the media_type value set ('image', 'video', 'document' for PDFs), the limit default and max (30/100), and that workspace_id accepts an ID or a name. The three params left unexplained (context, llm_model, conversation_id) are all analytics/infra params already documented in the schema, so the gap is not costly.

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 opening sentence names the resource precisely — the workspace media library covering images, videos and PDFs — and the title/annotation confirm it is a read-only listing. It does not explicitly say 'list' in the body or name a sibling it is not (e.g., vs. add_media or attach_media), but the 'URLs to attach' phrasing implicitly positions it upstream of attach_media.

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?

Usage is implied by 'with URLs to attach,' suggesting this is the discovery step before attach_media, but no explicit when-to-use / when-not-to-use statement or named alternative is given. An agent has to infer routing from the sibling list.

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

All Antwork toolsInspect
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