Skip to main content
Glama

Rename folder

rename_folder

Rename a Microsoft 365 Outlook mail folder by specifying its name, display path, or folder ID and providing the new name.

Instructions

Rename a folder.

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": {
      "folder": "<folder>",
      "name": "<name>"
    },
    "name": "rename_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew name
folderYesFolder to rename. Accepts a well-known name (inbox, drafts, sentitems/sent, deleteditems/trash, junkemail/junk, archive, outbox), a display name or path such as "Inbox/Projects", or a folder ID from list_folders

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that (name collisions, idempotency, effect on existing paths are unstated), so it fails to earn credit for context above the annotations.

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

Conciseness3/5

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

It is a single short sentence with no filler, but it is also under-specified rather than genuinely concise – the words carry no information beyond the title.

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?

This is a simple two-parameter mutation with full schema coverage and clear annotations, so the definition is minimally sufficient to invoke correctly. It lacks any note on collision behavior or confirmation, but nothing critical is missing for a call to succeed.

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 100%; the `folder` parameter's own description covers well-known names, paths, and folder IDs, and `name` is documented. The description contributes nothing extra, so the baseline 3 applies.

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

Purpose2/5

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

"Rename a folder." restates the tool name and title with no additional specificity. It conveys the verb and resource but nothing about scope, so an agent gains no differentiation from siblings like move_folder or delete_folder.

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?

No when-to-use guidance, no prerequisites, no mention of alternatives or when renaming is inappropriate versus moving or creating a folder. The agent must infer usage entirely from the name.

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