Skip to main content
Glama

delete-onedrive-file

Destructive

Delete a OneDrive file or item by providing the drive ID and item ID.

Instructions

Delete navigation property items for drives

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
If-MatchNoETag
driveIdYesPath parameter: driveId
driveItemIdYesPath parameter: driveItemId
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior2/5

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

Annotations already indicate destructiveHint=true, so the description adds minimal behavioral context. It does not clarify whether deletion is permanent, moves to recycle bin, or requires specific permissions. The description adds no value beyond what annotations provide.

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

Conciseness2/5

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

The description is a single 5-word sentence, which is concise but not informative. It lacks structure and does not provide enough detail to be useful. True conciseness should include essential information, which is missing.

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?

Given the tool's complexity (5 parameters, no output schema), the description is severely incomplete. It does not explain the deletion behavior, return values, or required context. The agent cannot determine how to invoke the tool correctly based on this description.

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

Parameters2/5

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

Despite 100% schema coverage, the description adds no semantic value to the parameters. It does not explain the role of If-Match, driveId, driveItemId, includeHeaders, or excludeResponse. The schema descriptions are minimal, and the description fails to compensate.

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?

The description 'Delete navigation property items for drives' is vague and uses technical jargon ('navigation property items') that does not clearly convey the tool's purpose. It fails to specify that it deletes a file or item from OneDrive, which is essential for distinguishing it from sibling delete tools.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus other delete tools (e.g., delete-calendar-event, delete-mail-message) or any prerequisites or context.

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

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/Softeria/ms-365-mcp-server'

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