Skip to main content
Glama

List your Artifacts

list_artifacts
Read-onlyIdempotent

List Artifacts you own (scope owned, the default), ones shared with you (shared), or both (all), newest first. Each item carries its id, title, who can open it, and its URL.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this type.
limitNoPage size, default 25.
scopeNoDefault owned.
cursorNonext_cursor from a prior page.

Output Schema

NameRequiredDescriptionDefault
itemsYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / expires_at
      Added value: +{
      +  "description": "When it is deleted, as its owner asked; absent when it is kept.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / icon_image_url
      Added value: +{
      +  "description": "The page icon set with icon_image; null for the Bisque icon.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds non-annotation context: results are ordered newest first and each item carries its id, title, access scope, and URL — useful for an agent reasoning about ordering and follow-up calls.

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 compact sentences: the first front-loads the scope options and ordering, the second summarizes item contents. No filler, no repetition of annotation or schema content beyond what aids comprehension.

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?

With an output schema present, return-value detail is not required, and the description still summarizes item fields and ordering. Scope semantics and defaults are covered; only pagination behavior beyond the cursor parameter is left to the schema, which is acceptable for a simple read-only 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?

Schema description coverage is 100%, so all four parameters are already documented, including defaults for scope and limit and the cursor semantics. The description restates the scope default but adds nothing about the type filter or limit bounds, so it does not exceed the schema baseline.

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 Artifacts") and immediately narrows scope to owned/shared/all, which separates it from the singular get_artifact and from list_presentations. It never names a sibling explicitly, so it falls just short of full differentiation.

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 explains what each scope value selects and that 'owned' is the default, which is genuine guidance for choosing behavior. However, it offers no guidance on when to use this tool versus alternatives such as get_artifact or list_artifact_threads, and no exclusions or prerequisites.

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.

Resources