Skip to main content
Glama

highlight_range

Highlight a range of lines in a Neovim buffer with a specified color. Visual annotation only, does not modify buffer content. Specify file, start and end lines, and optional color.

Instructions

Add a colored line highlight to a Neovim buffer. This is a visual annotation only — it does not modify buffer content and is not persisted to disk. Highlights stack; calling this multiple times adds more highlights without removing previous ones.

file: path relative to Neovim's cwd (as shown in get_state buffers). The buffer must already be open in Neovim; returns an error otherwise. start_line: first line to highlight (1-indexed, inclusive). end_line: last line to highlight (1-indexed, inclusive). Out-of-range values are clamped. If start_line > end_line they are swapped. color: any hex color (e.g. "#3b4048") or Neovim color name (e.g. "DarkGreen"). Defaults to "#3b4048".

Use this for a single highlight. Use highlight_ranges to apply multiple highlights in one call. Use clear_highlights to remove all highlights from a buffer.

Returns {highlighted} with the number of lines highlighted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYes
start_lineYes
end_lineYes
colorNo#3b4048
Behavior5/5

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

With no annotations, the description fully discloses behavior: visual only, not persisted, highlights stack, line clamping and swapping, and return format {highlighted}. No misleading or omitted traits.

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?

Concise and well-structured: front-loaded purpose, then behavioral traits, parameter explanations, usage guidance, and return value. No redundancy, every sentence earns its place.

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

Completeness5/5

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

Comprehensive given no output schema or annotations: covers all necessary aspects (purpose, behavior, parameters, return, usage context) for correct agent invocation.

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

Parameters5/5

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

Schema coverage is 0%, so description must explain parameters. It provides detailed semantics for all 4 params: file path relative to cwd, line indices (1-indexed, inclusive, with clamping and swapping), and color (hex or Neovim name with default).

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 adds a colored line highlight to a Neovim buffer, specifies it is a visual annotation only (no content modification or persistence), and distinguishes from siblings highlight_ranges and clear_highlights.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (single highlight) versus highlight_ranges (multiple) and clear_highlights (remove all), and notes the file must already be open in Neovim or it returns an error.

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/paulburgess1357/nvim-mcp'

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