Skip to main content
Glama
Sign In
Files.com MCP Server

Files.com MCP Server

Official
by Files-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Bundle Download

List_Bundle_Download
Read-only

Retrieve a list of downloads for a specific share link bundle, with optional field selection for the response.

Instructions

List Share Link Downloads

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

Input Schema

NameRequiredDescriptionDefault
bundle_idNoBundle ID
fieldsNoOptional list of attribute names to include as columns in the response table. When omitted, a sensible default set is used. Useful for narrowing wide entities or surfacing fields not in the default.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.65

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=true. The description adds no behavioral details such as what data is returned, authentication requirements, or side effects. Since coverage from annotations is already present, description adds minimal value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, concise but lacking structure. It is front-loaded but omits important operational context. Every word earns its place, but the brevity sacrifices completeness.

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?

The description does not explain the tool's purpose in the context of bundle downloads or share links. It fails to clarify what 'Share Link Downloads' are, how bundle_id filters results, or what the output (with existing output schema) contains. Incomplete for a list operation.

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 coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning or context for bundle_id or fields beyond what the schema provides. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List Share Link Downloads' uses the verb 'List' matching the tool name, but the resource is ambiguous. The tool name includes 'Bundle' but the description mentions 'Share Link Downloads', creating potential confusion. It does not clearly differentiate from sibling list tools like List_Bundle or List_Bundle_Notification.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, when not to use, or relationship to other sibling tools like List_Bundle or List_Bundle_Notification.

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

Deploy Server

Other Tools