Skip to main content
Glama

overleaf_delete_path

Deletes a file or folder from an Overleaf project using the project ID, URL, or title and the remote path to remove.

Instructions

Delete a file or folder from an Overleaf project.

Args: project: Overleaf project ID, project URL, or exact project title. remote_path: File or folder path inside Overleaf to delete.

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": {
      "project": "<project>",
      "remote_path": "<remote_path>"
    },
    "name": "overleaf_delete_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes
remote_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a destructive mutation and largely does not meet it: it never says deletion is irreversible, whether deleting a folder is recursive, what happens to a non-existent path, or what permissions are required. "File or folder" hints that directory removal is in scope but leaves the recursive semantics ambiguous, which is the most consequential unknown for a delete tool.

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

Conciseness4/5

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

One summary sentence followed by a compact Args list, front-loaded with the verb and resource. Nothing is padded, and the parameter notes are short; the only slight inefficiency is that the summary and the Args block partially overlap in naming the target.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the two required parameters are documented. However, for an irreversible delete operation with no annotations, the definition omits recursive-folder behavior, failure modes, and confirmation semantics, leaving gaps an agent would want filled before invoking it.

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?

Schema coverage is 0%, so the Args block does real work: it tells the agent that `project` accepts an ID, a URL, or an exact title, and that `remote_path` is a path inside the project for either a file or a folder. That is meaningful added meaning beyond bare string-typed properties, though it omits whether remote_path is absolute or project-root-relative.

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?

"Delete a file or folder from an Overleaf project" names a specific verb (delete) and resource (file/folder) scoped to a project, which clearly separates it from siblings like overleaf_read_file, overleaf_write_file, and overleaf_list_files. It stops short of explicitly naming a contrasting sibling, so it is clear but not maximally differentiated.

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?

The description states what the tool does but gives no guidance on when to use it versus alternatives such as overleaf_write_file for truncation or overleaf_upload_file for overwrite, and no prerequisites. The only implicit guidance is that a target path must already exist, which the agent has to infer.

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