Skip to main content
Glama
Glitch-Gaming-Platform

Glitch MCP

Official

List Artifacts

glitch_list_artifacts
Read-onlyIdempotent

List downloadable files and hosted report artifacts from a Glitch Agent run.

Instructions

List downloadable files and hosted report artifacts for a Glitch Agent run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
title_idNoGlitch game title id. Omit only after calling glitch_select_title or setting GLITCH_TITLE_ID.
run_idYesGlitch agent run id.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, making safety clear. The description adds context about the content of artifacts (downloadable files and reports) but does not discuss any additional behavioral traits (e.g., error states, pagination).

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?

The description is a single, concise sentence that immediately conveys the purpose. No unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple listing tool with two parameters and no output schema, the description is adequate but does not mention the return format or any potential limitations. Given the presence of thorough annotations, it meets minimal requirements but could be more complete.

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 100% with descriptions for both title_id and run_id. The tool description does not add any extra meaning or usage hints beyond what the schema already provides.

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?

The description clearly states the verb 'List' and the specific resources 'downloadable files and hosted report artifacts' for a 'Glitch Agent run'. It distinguishes from siblings like glitch_list_titles and glitch_list_pending_actions.

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 implies usage for retrieving artifacts of a run, but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Glitch-Gaming-Platform/Glitch-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server