Skip to main content
Glama

list_space_files

List files, Drive items, and links shared in recent threads of a Google Chat space to locate shared resources.

Instructions

List files, Drive items and links shared in the latest page_size threads.

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": {
      "space_id": "<space_id>"
    },
    "name": "list_space_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_dmNo
space_idYes
page_sizeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/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 does disclose one real behavioral trait beyond the schema: results are drawn only from the latest page_size threads rather than the whole space, which matters for completeness expectations. It omits permission/auth requirements, ordering, and the DM-vs-channel distinction, so it under-delivers for an unannotated tool.

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?

A single front-loaded sentence with no filler. It is efficient, though part of that brevity comes from under-specification rather than disciplined editing.

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

Completeness2/5

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

An output schema exists, so return values needn't be explained, but for a 3-parameter tool with zero schema coverage and no annotations the description leaves too much unexplained: the is_dm flag, space scoping, and pagination semantics for the file list itself are all absent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain all three parameters. It only touches page_size, and in a non-obvious way (it bounds how many threads are scanned, not how many files are returned), while space_id and is_dm receive no explanation at all — the DM flag in particular is entirely opaque.

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 (List) and enumerates the resources returned (files, Drive items, links), which clearly separates it from siblings such as list_members and list_sections. The scope clause 'shared in the latest page_size threads' is ambiguous but the core action 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 Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g. search_messages or read_thread), no prerequisites, and no exclusions. The agent must infer usage purely from the tool name and the one-sentence purpose.

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