mcp-slack-crunchtools

Slack List Files

slack_list_files

Read-only

Lists files in a Slack workspace with metadata only, letting you filter by channel, uploader, file type, and creation date range. Paginate results without downloading file content.

Instructions

List files in the Slack workspace (metadata only, no content download).

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1)
`count`	No	Results per page, 1-100 (default: 100)
`ts_to`	No	Filter files created before this Unix timestamp
`types`	No	Filter by types (comma-separated: spaces, snippets, images, gdocs, zips, pdfs, all)
`ts_from`	No	Filter files created after this Unix timestamp
`user_id`	No	Filter by uploader's user ID
`channel_id`	No	Filter by channel ID

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.4.0Oct 22, 2026

addedInput schema / properties / channel_id / description
```
Added value: +"Filter by channel ID"
```

addedInput schema / properties / count / description

Added value: +"Results per page, 1-100 (default: 100)"

addedInput schema / properties / page / description
```
Added value: +"Page number (default: 1)"
```

addedInput schema / properties / ts_from / description

Added value: +"Filter files created after this Unix timestamp"

addedInput schema / properties / ts_to / description

Added value: +"Filter files created before this Unix timestamp"

addedInput schema / properties / types / description

Added value: +"Filter by types (comma-separated: spaces, snippets, images, gdocs, zips, pdfs, all)"

addedInput schema / properties / user_id / description
```
Added value: +"Filter by uploader's user ID"
```

First observedv0.2.0Sep 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile. The description adds useful behavioral context by clarifying that results are metadata only and do not include file content, but it does not discuss pagination behavior, rate limits, or auth requirements beyond what the schema already shows.

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?

The description is a single front-loaded sentence with no wasted words. The critical clarification about metadata-only scope is included immediately.

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 an output schema present and full parameter documentation, the description is nearly complete for a listing tool. It could be stronger by naming when to choose this over sibling file-access tools, but nothing essential for correct invocation is missing.

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%, so every parameter is already documented with purpose and defaults. The description adds no extra meaning beyond the schema, which is acceptable given the schema does the heavy lifting.

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 states a specific verb (List) and resource (files) scoped to the Slack workspace, and clarifies that only metadata is returned. It clearly separates this from a content-download operation, though it does not explicitly distinguish itself from sibling tools like slack_get_file_info or slack_search_messages.

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 implied by the phrase 'List files in the Slack workspace', and the metadata-only note sets a boundary against content retrieval. However, there is no explicit guidance on when to use this tool versus slack_get_file_info, slack_search_messages, or the channel-specific listing siblings.

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

Deploy Server