Skip to main content
Glama

List Grok Bot artifacts

list_grok_artifacts

List artifact files attached by Grok Bot to a request, including name, size, SHA-256, and content type, so you can inspect or retrieve reports, source lists, JSON, CSV, and XLSX outputs.

Instructions

List the artifact files Grok Bot attached to a request (name, size in bytes, sha256, content type). Artifacts hold the full detail: reports, source lists, JSON, CSV, XLSX.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request_id": "<request_id>"
    },
    "name": "list_grok_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe request_id of the task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the shape of what is returned (metadata only, not file content), which is valuable, but says nothing about what happens if the request is not yet complete, whether an empty list is possible, or any auth/rate constraints.

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 tight sentences with no filler: the operation and its returned fields come first, then the rationale for using artifacts at all. Nothing is repeated from the schema.

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?

For a one-parameter read tool with no output schema, enumerating the return fields in prose compensates well for the missing output schema. The remaining gap is edge-case behavior (pending requests, empty artifact lists), which is minor but would have made it 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 description coverage is 100% and the single request_id parameter is already documented as "The request_id of the task." The description adds no format, origin, or lookup guidance for request_id (e.g., where to obtain it), so baseline 3 applies.

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 the artifact files Grok Bot attached to a request") and even enumerates the returned fields (name, size in bytes, sha256, content type), so the agent knows exactly what it gets. It does not explicitly contrast itself with the sibling download_grok_artifacts, so metadata-listing vs. content-fetching must be inferred from the verb.

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?

"Artifacts hold the full detail: reports, source lists, JSON, CSV, XLSX" implies you should come here when the summary result is insufficient, which is real usage guidance. But it never states prerequisites (e.g., that the request must have finished) or names download_grok_artifacts as the next step for retrieving content, leaving the choice of tool implicit.

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