Skip to main content
Glama

artifacts_get

Read-onlyIdempotent

Fetch an artifact's metadata by id or slug — title, access level, version, view count, URL, and events: what visitors pressed on the published page (elements marked data-track, see artifacts.create), per name with count and first/last time. Set recent_events to also get the last presses one by one. Set include_html=true to also return the latest HTML body (so you can read-then-edit before calling artifacts.update).

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

Input Schema

NameRequiredDescriptionDefault
slugNoThe artifact slug. Pass this or artifact_id.
artifact_idNoThe artifact id. Pass this or slug.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
include_htmlNoIf true, include the latest version's HTML body.
recent_eventsNoHow many of the latest presses to list one by one (name + time, newest first), 0-200. Totals per name are always returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / recent_events
      Added value: +{
      +  "description": "How many of the latest presses to list one by one (name + time, newest first), 0-200. Totals per name are always returned.",
      +  "type": "integer"
      +}
  2. 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"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description adds rich return-value context: exact metadata fields, event semantics tied to data-track elements, per-name counts with first/last timestamps, and the read-then-edit use case for include_html. This goes well beyond the annotations.

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?

Purpose and key behaviors are front-loaded, and the parenthetical event explanation is valuable despite adding length. A few phrases restate schema details, but overall the description is appropriately sized and structured.

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 description usefully explains the returned metadata and events. Parameter details are covered by the schema; only in_workspace behavior is left entirely to the schema, which is sufficient.

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 100%, so the schema already defines all parameters. The description adds meaningful use-case context for include_html (read-then-edit before artifacts.update) and clarifies output behavior for recent_events, though it does not mention in_workspace.

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 (Fetch) and resource (artifact metadata by id or slug), then enumerates the returned metadata fields. It references artifacts.create and artifacts.update for related workflows, though it does not explicitly distinguish itself from artifacts_list.

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?

Gives clear context for optional parameters: use include_html to read-then-edit before artifacts.update, and recent_events to get individual presses. It does not state when not to use this tool or when artifacts_list is preferable.

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.