Skip to main content
Glama

manage_entity

Destructive

Create folders and rename, move, or delete Overleaf project entities. Validates paths and names before changes so invalid moves or duplicate names are blocked.

Instructions

Create a folder, rename, move, or delete an entity. Deletion requires confirmPath to exactly equal path. A name already used in the target folder (the entity's own included), and a folder moved into itself or one of its subfolders, are INVALID_ARGUMENT before anything is sent.

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": {
      "projectId": "<projectId>",
      "action": "<action>",
      "path": "<path>"
    },
    "name": "manage_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesProject-relative path using forward slashes
actionYes
newNameNo
projectIdYesOverleaf project ID
confirmPathNo
destinationFolderPathNo

Output Schema

NameRequiredDescriptionDefault
idNo
actionYes
createdNo
writeModeYes
trackChangesActiveYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds real value beyond that. It discloses that validation happens client-side before any request ('INVALID_ARGUMENT before anything is sent') and spells out two concrete rejection conditions: name collisions in the target folder (including the entity's own name) and moving a folder into itself or a descendant. It still does not say what happens on confirmation mismatches (error type) or whether moves preserve contents.

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?

Two sentences, zero filler, with the operations front-loaded and the validity constraints compressed into the second sentence. Every clause carries a distinct rule an agent needs.

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?

For a six-parameter destructive tool with an output schema, the description covers the deletion path and pre-flight validation well but omits how rename and move consume newName and destinationFolderPath, and whether those are required per action. An agent can call delete confidently but must guess the parameter shape for the other three actions.

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 description coverage is only 33%, and the description compensates for exactly one parameter: confirmPath must exactly equal path. It leaves newName, destinationFolderPath, and their association with the rename and move actions undocumented in both the schema and the prose, which is the main ambiguity remaining.

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?

The description names a specific resource (entity: folder/file) and enumerates the four operations verb-first: create folder, rename, move, delete. That is clear enough for an agent to know it is a multi-action mutation tool. It does not differentiate itself from siblings such as delete_entities or create_file, so it stops short of a 5.

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?

Usage is implied by the action enum rather than stated: an agent must infer that create_folder/rename/move/delete map to the listed verbs. The one explicit guideline is the confirmPath requirement for deletion, which is genuinely useful, but there is no statement of when to prefer this tool over delete_entities or other file-level tools.

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