Skip to main content
Glama

artifacts_list

Read-onlyIdempotent

List the workspace's artifacts (most-recently-updated first): title, url, access level, version, view count, and how many presses visitors made on it (event_count, last_event_at; details in artifacts.get). Soft-deleted artifacts are excluded.

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

Input Schema

NameRequiredDescriptionDefault
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description is not carrying the safety burden. It still adds real value beyond them: soft-deleted artifacts are excluded, results are ordered by recency, and event_count/last_event_at are described as visitor 'presses' with a semantic explanation rather than bare field names.

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?

A single dense sentence with the action front-loaded, followed by the return-field list, the routing pointer, and the exclusion rule. Every clause carries information and nothing is repeated.

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?

No output schema exists, so the inline field enumeration does necessary work, and exclusion/ordering rules are stated. It does not address result-size limits or truncation behavior, which is the one open question for an unpaginated list.

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?

One optional parameter with 100% schema description coverage, so the schema already explains the in_workspace override. The description says 'the workspace's artifacts' but does not elaborate on the override semantics, leaving it at the baseline for well-documented schemas.

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?

Specific verb and resource ('List the workspace's artifacts') plus scope, default sort order ('most-recently-updated first'), and the exact fields returned. It also redirects detail-seeking to artifacts.get, so it is distinguishable from that sibling without opening a schema.

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?

Clear context for use (workspace artifact inventory) and an explicit routing hint: field details live in artifacts.get. It never states exclusions or an alternative for cross-workspace listing, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.