Skip to main content
Glama
thehzuo

web-gui-mcp

by thehzuo

list_artifacts

Retrieve a paginated list of stored HTML artifacts from the in-memory repository. Specify a limit to control the number of results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
artifactsYes

Implementation Reference

  • The main handler function for the list_artifacts tool. Takes ListArtifactsInput and a MemoryArtifactStore, calls store.list(limit) to retrieve stored artifacts sorted by updated_at descending, and returns ListArtifactsOutput.
    def list_artifacts_handler(
        input_data: ListArtifactsInput,
        store: MemoryArtifactStore,
    ) -> ListArtifactsOutput:
        return ListArtifactsOutput(
            artifacts=[
                ArtifactListItem(
                    artifact_id=item.artifact_id,
                    title=item.spec.title,
                    artifact=item.spec.artifact,
                    created_at=item.created_at.isoformat(),
                    revision=item.revision,
                )
                for item in store.list(limit=input_data.limit)
            ]
        )
  • Registration of the list_artifacts tool via @mcp.tool() decorator. Delegates to list_artifacts_handler with the shared store instance.
    @mcp.tool()
    def list_artifacts(input: ListArtifactsInput) -> ListArtifactsOutput:
        return list_artifacts_handler(input, store)
  • Input schema for list_artifacts with an optional 'limit' field (default 20, range 1-100).
    class ListArtifactsInput(ToolBaseModel):
        limit: int = Field(default=20, ge=1, le=100)
    
    
    class ArtifactListItem(ToolBaseModel):
        artifact_id: str
        title: str
        artifact: str
        created_at: str
        revision: int
    
    
    class ListArtifactsOutput(ToolBaseModel):
        artifacts: list[ArtifactListItem]
  • ArtifactListItem model used in ListArtifactsOutput, containing artifact_id, title, artifact type, created_at timestamp, and revision number.
    class ArtifactListItem(ToolBaseModel):
        artifact_id: str
        title: str
        artifact: str
        created_at: str
        revision: int
    
    
    class ListArtifactsOutput(ToolBaseModel):
        artifacts: list[ArtifactListItem]
  • Output schema for list_artifacts containing a list of ArtifactListItem objects.
    class ListArtifactsOutput(ToolBaseModel):
        artifacts: list[ArtifactListItem]
  • The store.list() method used by list_artifacts_handler. Returns up to `limit` artifacts sorted by updated_at descending.
    def list(self, limit: int = 20) -> list[StoredArtifact]:
        return sorted(
            self._artifacts.values(),
            key=lambda item: item.updated_at,
            reverse=True,
        )[:limit]
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/thehzuo/gui-mcp'

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