Skip to main content
Glama
larrygmaguire-hash

Slack Note Capture MCP Server

slack_get_file

Retrieve file details and download URLs from Slack to access voice notes and documents shared in channels.

Instructions

Get information about a file shared in Slack, including download URL. Use this to retrieve voice notes and documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_idYesThe Slack file ID.

Implementation Reference

  • The handler implementation for the `slack_get_file` tool, which calls `slack.files.info` to retrieve file metadata.
    case "slack_get_file": {
      const fileId = args.file_id;
    
      const result = await slack.files.info({
        file: fileId,
      });
    
      const file = result.file;
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                id: file.id,
                name: file.name,
                title: file.title,
                mimetype: file.mimetype,
                size: file.size,
                url_private: file.url_private,
                url_private_download: file.url_private_download,
                created: new Date(file.created * 1000).toISOString(),
                user: file.user,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • The definition and input schema for the `slack_get_file` tool.
    {
      name: "slack_get_file",
      description:
        "Get information about a file shared in Slack, including download URL. Use this to retrieve voice notes and documents.",
      inputSchema: {
        type: "object",
        properties: {
          file_id: {
            type: "string",
            description: "The Slack file ID.",
          },
        },
        required: ["file_id"],
Behavior3/5

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

With no annotations provided, the description carries full behavioral burden. It successfully discloses that the tool returns a 'download URL' (distinguishing from content retrieval), but omits authentication requirements, rate limits, privacy constraints, or what happens if the file is private/deleted.

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 efficient sentences with zero waste: first defines the operation and return value, second states applicable file types. Information is front-loaded and appropriately sized for a single-parameter tool.

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 simple read operation with one well-documented parameter, the description is reasonably complete. It compensates for the missing output schema by specifying the key return value (download URL), though it could mention other metadata fields returned (e.g., file name, size, creator).

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?

Input schema has 100% description coverage for the single 'file_id' parameter, establishing a baseline of 3. The description adds no specific parameter guidance (format, where to obtain ID, examples), but doesn't need to given the complete schema self-documentation.

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 clearly states the tool retrieves 'information about a file... including download URL' and mentions specific use cases (voice notes, documents). However, it lacks explicit differentiation from sibling tool 'slack_download_file', leaving ambiguity about whether this returns metadata/URLs versus actual binary content.

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?

Provides implied usage guidance by referencing specific file types ('voice notes and documents'), but fails to specify when to use this versus 'slack_download_file' or state that this returns metadata/URLs rather than downloaded content.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/larrygmaguire-hash/slack-note-capture'

If you have feedback or need assistance with the MCP directory API, please join our Discord server