Gemini MCP Server

by salviz

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

gemini_list_files

List files uploaded to the Gemini API with a configurable page size to control the number of results returned.

Instructions

List files uploaded to the Gemini Files API

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": "gemini_list_files"
  }
}

Input Schema

Name	Required	Description	Default
`pageSize`	No	Number of files to list (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jun 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only states it lists files but does not mention that it is read-only, whether it requires authentication, or any details about pagination or rate limits. The parameter 'pageSize' hints at pagination but is not explained.

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?

The description is a single, clear sentence that is front-loaded and efficient. It could be slightly expanded to include behavioral details without becoming verbose, but it is appropriately sized for a simple tool.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is adequate but lacks details about the return value (e.g., list of file objects, metadata). It covers the basic purpose but leaves out context about what the output contains.

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%; the parameter 'pageSize' is described in the schema as 'Number of files to list (default: 20)'. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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', the resource 'files', and the context 'Gemini Files API'. It distinguishes this tool from siblings like gemini_upload_file and gemini_delete_file by specifying it lists files.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus others, no prerequisites, and no exclusions. There is no mention of alternatives or context for appropriate use.

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