Skip to main content
Glama

List Uploads Tool

list_uploads
Read-only

List the team's Uploads, newest first: ready ones with their url for , and ones still waiting for their file with their upload links. Also shows the storage they use against the team's limit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true), but the description still adds real behavioral content: result ordering (newest first), a two-state model (ready vs. awaiting file), the concrete artifacts returned (an img src URL and upload links), and a storage-usage-vs-limit summary. It omits pagination or result-count limits, which matters for a zero-parameter list tool that can return everything.

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?

One dense sentence with no wasted clauses, and the key facts (verb, resource, ordering) are front-loaded. The packed enumeration of ready/pending states plus the storage clause makes it slightly harder to parse than a short bulleted split would be.

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 no output schema, the description must carry the return-value burden alone, and it does so by describing both entry states, the URLs each carries, and the storage summary. It falls short only on volume and pagination behavior for what is an unbounded team-wide listing.

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?

The tool takes no parameters, so the schema baseline of 4 applies and the description has nothing further to disambiguate. It correctly implies the call is scoped to the caller's team with no filtering arguments.

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?

The description names a specific verb and resource ("List the team's Uploads") plus a scope (team-level, newest first), which separates it cleanly from the mutation siblings create_upload and delete_upload. It does not explicitly contrast with any list-type sibling, but the resource noun is unambiguous.

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?

Usage is only implied: an agent can infer this is the read path for inspecting existing uploads, and the mention of "ones still waiting for their file" hints at a post-create status check. There is no explicit when-to-use statement, no exclusions, and no pointer to create_upload or to any get/fetch alternative.

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