mcp-overleaf

Rename or move a file

move_file

Rename or move files and folders inside an Overleaf project, creating any missing target folders. Update your \input or \include references after the change.

Instructions

Rename and/or move a file or folder within the project, e.g. intro.tex → sections/introduction.tex. Missing target folders are created. Remember to update \input/\include references. Uses Git; falls back to the opt-in web mode if enabled.

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": {
      "path": "<path>",
      "new_path": "<new_path>"
    },
    "name": "move_file"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Current path.
`project`	No	Project ID or Overleaf project URL (or project name in web mode). Defaults to OVERLEAF_PROJECT_ID.
`new_path`	Yes	New path.
`commit_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses side effects (missing target folders created) and backend behavior (Git with an opt-in web fallback), which are real behavioral traits. However, it omits overwrite semantics for an existing target, reversibility, and permission/auth needs — critical gaps for a mutation tool.

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 tight sentences, front-loaded with the core action and example, followed by side-effect and backend notes. Every sentence adds distinct information with no padding.

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?

A mutation tool with no annotations and no output schema, so the description is the sole source of behavioral detail. It covers folder creation, reference updates, and backend mode, but leaves overwrite behavior and failure/auth conditions unaddressed.

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 75%, so the schema already documents most parameters, and the example (intro.tex → sections/introduction.tex) illustrates path/new_path format. But commit_message is undocumented in both places, and no syntax or format detail is added beyond the schema baseline.

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 and resource ('rename and/or move a file or folder within the project') and reinforces it with a concrete path example. An agent can distinguish this from write_file/edit_file without opening a schema.

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 an actionable caveat ('update \input/\include references') and notes folder auto-creation, implying usage context, but never says when to use this over siblings like write_file or delete_file, nor any when-not condition. Usage is implied rather than explicit.

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

Deploy Server