xlide-excel-word-powerpoint-access-office-vba-mcp

Overview Schema Source Related Servers Discussions Admin

Notes and comments

xlide_manage_comment

DestructiveIdempotent

Manage Excel cell comments: read notes and threaded conversations, add or update notes, reply to threads, resolve them, or remove comments from a worksheet.

Instructions

Lists, writes, answers or removes the comments on a worksheet's cells. Excel has two kinds: a note, the yellow box that shows on hover, and a threaded comment, the conversation on the Review tab with replies and a resolved state. action='list' reads both and changes nothing. 'set' writes a note, replacing one already on the cell, or with kind='thread' starts a conversation; 'reply' and 'resolve' act on a thread; 'remove' takes either kind off the cell. Use a note to explain a cell to whoever reads the workbook next.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cell`	No	The cell, such as B4. For list, empty lists the sheet.
`kind`	No	For set: 'note' or 'thread'.	note
`text`	No	For set and reply: what the comment says.
`sheet`	Yes	Worksheet name, matched without case.
`action`	No	list, set, reply, resolve or remove.	list
`author`	No	Who wrote it, as the workbook shows the name.	Agent
`visible`	No	For a note: shown all the time, not only on hover.
`resolved`	No	For resolve: false opens a thread again.
`file_path`	Yes	Absolute path to the Excel file.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0Sep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With annotations declaring destructiveHint=true and readOnlyHint=false, the description adds crucial behavioral detail: 'list' changes nothing, 'set' replaces an existing note, and 'reply'/'resolve' act on threads. It also clarifies the resolved state, going beyond 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.

Conciseness4/5

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

The description is moderately detailed but front-loads the primary purpose and uses a logical flow from overall capability to action specifics. It is not excessively verbose and each sentence adds value, though it could be slightly tighter.

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

Completeness4/5

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

Given the 9 parameters, rich annotations, and an output schema, the description covers all actions, the note/thread distinction, and parameter interplay. It does not describe return values, but the output schema handles that. It is complete enough for an agent to use correctly.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the semantics of 'action' values (list/set/reply/resolve/remove), 'kind' (note vs. thread), and the effect on existing comments, which is not evident from parameter descriptions alone.

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?

The description clearly states the tool lists, writes, answers, or removes comments on worksheet cells, with a specific verb and resource. It distinguishes notes from threaded comments, making its purpose unambiguous and separate from any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on when to use a note vs. a thread ('Use a note to explain a cell to whoever reads the workbook next') and explains each action's role. It does not explicitly mention alternative tools, but no sibling handles comments, so the context is sufficient.

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

Deploy Server