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

Overview Schema Source Related Servers Discussions Admin

Hyperlinks

xlide_manage_hyperlink

DestructiveIdempotent

Manage hyperlinks in Excel worksheets: list, add, or remove links to URLs, files, or workbook locations. Specify target or internal location, optional display text.

Instructions

Lists, adds or removes hyperlinks on a worksheet. A link either goes out to a target, which is a URL or a file path, or inside the workbook to a location such as 'Summary!A1'. Pass one or the other. The cell's displayed text is separate from the link and is left alone unless you pass display.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sheet`	Yes	Worksheet name, matched without case.
`action`	No	list, add or remove.	list
`target`	No	For add: a URL or file path to open.
`display`	No	For add: text to put in the cell.
`tooltip`	No	For add: the hover text.
`location`	No	For add: a place in this workbook, like Summary!A1.
`file_path`	Yes	Absolute path to the Excel file.
`cell_range`	No	For add and remove: the cell or range.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already signal mutability, destructiveness, and idempotence. The description adds useful behavioral context beyond that: the distinction between target and location, and the fact that displayed cell text is preserved unless 'display' is explicitly provided. This materially helps an agent predict side effects.

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?

Four sentences, each earning its place: the action scope, the two link kinds, the mutual-exclusion rule, and the display-text caveat. No filler or repetition of schema details.

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 an output schema, full parameter descriptions, and annotations, the description covers the key relationships an agent needs to call the tool correctly. It could be more explicit about action-specific required parameters, but the schema already documents those per-action notes.

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 target/location mutual exclusivity and the independence of display text, which are not encoded in the individual parameter descriptions.

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 opens with a specific verb and resource: 'Lists, adds or removes hyperlinks on a worksheet.' This clearly distinguishes it from the many sibling manage_* tools, none of which target hyperlinks.

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?

The description gives clear operational context, explaining that a hyperlink can be external or internal and instructing to 'Pass one or the other.' It does not explicitly name alternatives, but no sibling tool covers hyperlinks, so the usage context is sufficiently clear.

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

Deploy Server