Skip to main content
Glama
YanceyOfficial

Obsidian iCloud MCP

remove_multiple_files

Delete multiple files from an Obsidian vault stored in iCloud Drive by specifying their paths, enabling efficient file management within the Model Context Protocol framework.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYes

Implementation Reference

  • The main handler function that parses the input arguments using RemoveMultipleFilesArgsSchema, deletes the specified files using fs.unlink in parallel, and returns a standardized content response with the operation result.
    export async function removeMultipleFiles(args?: Record<string, unknown>) {
      const parsed = RemoveMultipleFilesArgsSchema.safeParse(args)
      if (!parsed.success) {
        throw new Error(
          `Invalid arguments for remove_multiple_files: ${parsed.error}`
        )
      }
      const result = await Promise.all(
        parsed.data.paths.map((path) => fs.unlink(path))
      )
    
      return {
        content: [{ type: 'text', text: result }]
      }
    }
  • Zod schema defining the input for the tool: an object containing an array of file paths as strings.
    export const RemoveMultipleFilesArgsSchema = z.object({
      paths: z.array(z.string())
    })
  • src/index.ts:126-129 (registration)
    Tool registration in the ListToolsRequestHandler: defines the tool name, description from prompt, and converts schema to JSON schema for input validation.
      name: 'remove_multiple_files',
      description: removeMultipleFilesPrompt(),
      inputSchema: zodToJsonSchema(RemoveMultipleFilesArgsSchema) as ToolInput
    },
  • src/index.ts:191-193 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that routes calls to the removeMultipleFiles handler function.
    case 'remove_multiple_files': {
      return removeMultipleFiles(args)
    }
  • Prompt generator for the tool's description (currently empty string).
    export const removeMultipleFilesPrompt = () => ''
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/YanceyOfficial/obsidian-mcp'

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