Skip to main content
Glama
WilliamSmithEdward

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

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Hyperlinks

xlide_manage_hyperlink
DestructiveIdempotent

List, add, or remove hyperlinks on an Excel worksheet. Link cells to a URL, file path, or in-workbook location such as Summary!A1.

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
NameRequiredDescriptionDefault
sheetYesWorksheet name, matched without case.
actionNolist, add or remove.list
offsetNoFor list: links to skip.
targetNoFor add: a URL or file path to open.
displayNoFor add: text to put in the cell.
tooltipNoFor add: the hover text.
locationNoFor add: a place in this workbook, like Summary!A1.
file_pathYesAbsolute path to the Excel file.
cell_rangeNoFor add and remove: the cell or range.
max_resultsNoFor list: most links to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • addedInput schema / properties / max_results
      Added value: +{
+  "default": 300,
+  "description": "For list: most links to return.",
+  "maximum": 300,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "For list: links to skip.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation profile is partly covered. The description adds one genuine non-obvious behavior – the cell's displayed text is preserved unless 'display' is passed – but says nothing about whether add overwrites an existing link, whether remove is reversible, or the effect on cells outside cell_range.

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 short sentences, front-loaded with the verb/resource, then the branching rule, then the subtle display caveat. No filler and nothing buried.

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?

An output schema exists, so return values need no prose, and the description covers the three actions and the key parameter distinction. It is slightly thin for a 10-parameter, three-mode mutation tool in that it omits overwrite/reversibility semantics for add/remove.

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 per-parameter meaning is already documented and the baseline is 3. The description earns above baseline by explaining the relationship between 'target' and 'location' (external URL/file path vs intra-workbook reference) and clarifying that 'display' controls cell text independently of the link.

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?

Opens with a specific verb triple and resource: 'Lists, adds or removes hyperlinks on a worksheet.' The action vocabulary maps directly to sibling manage_* tools and an agent can distinguish it from manage_comment, manage_name, and manage_validation without reading further.

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?

The description explains the target-vs-location mutual exclusivity ('Pass one or the other'), which is real usage guidance for the add case, but it never states when to choose list vs add vs remove or any prerequisites such as the file needing to be closed or the cell needing to exist.

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

Deploy Server

Other Tools