ds-web-mcp

Upload files to DeepSeek

upload_files

Upload local files to a DeepSeek account and get file IDs for attaching them to chat prompts via refFileIds.

Instructions

Upload one or more local files (images, PDFs, documents, code, archives) to the DeepSeek account. Returns a file id per upload; pass those ids as refFileIds to the chat tool to attach them to a prompt. Max 104857600 bytes per file.

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": {
      "filePaths": "<filePaths>"
    },
    "name": "upload_files"
  }
}

Input Schema

Name	Required	Description	Default
`filePaths`	Yes	Absolute or relative local paths to upload.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write-scope is covered. The description adds genuinely new behavior: it persists artifacts into the account, returns a file id per file, and enforces a 104857600-byte per-file cap — all things the annotations cannot convey. It omits only partial-failure behavior when some paths fail.

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?

Three short sentences, zero filler, front-loaded with the action and resource. The downstream refFileIds instruction and the size limit both earn their place as decision-relevant facts.

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 one-parameter mutation with annotations and no output schema, the description supplies the missing pieces: return value (file id), consumption path (refFileIds), and hard limit. Only the multi-file atomicity question — whether one bad path fails the whole batch — is left unaddressed.

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

Parameters4/5

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

With one parameter at 100% schema coverage the baseline is 3, and the schema already documents 'Absolute or relative local paths'. The description earns a bump by constraining what those paths may point at (images, PDFs, documents, code, archives) and by stating the per-file size ceiling, which directly tells the agent how to split or reject inputs.

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?

States a specific verb ('Upload') and resource ('local files ... to the DeepSeek account'), enumerates accepted file categories, and is clearly distinct from the sibling list_files and chat tools. An agent can identify this as the write/ingest path without opening the schema.

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

Usage Guidelines4/5

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

Explicitly names the downstream step: 'pass those ids as refFileIds to the chat tool to attach them to a prompt,' which routes the agent correctly between upload and chat. It gives the positive workflow but stops short of stating exclusions (e.g., don't re-upload an existing file id, or what to do for remote URLs).

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

Deploy Server