Aspose.Cells Cloud MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Remove All Line Breaks

remove_all_line_breaks

Remove all line break characters from text in an Excel worksheet range, converting multi-line content into single-line text for cleaner data.

Instructions

Removes ALL line break characters (including \n, \r\n, \r) from text values within a specified range of a worksheet in an Excel file using Aspose.Cells Cloud API. Converts multi-line text into single-line text by deleting all newline characters. Returns True if the operation succeeds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_range`	No
`file_uuid`	Yes
`worksheet`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv26.4.1Sep 18, 2026
- removedInput schema / properties / file_token
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / file_uuid
```
Added value: +{
+  "type": "string"
+}
```
- changedInput schema / required
```
Previous value: -[
-  "file_token"
-]New value: +[
+  "file_uuid"
+]
```
First observedv26.4.0Aug 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries full behavioral burden. It explains the destructive transformation, specifies which characters are affected, notes the multi-line to single-line conversion, and states the return value on success. It could mention whether the operation is irreversible or whether it applies to the entire sheet when no range is given, but it is substantially transparent.

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 concise and front-loads the core behavior in the first sentence. The second sentence adds useful clarification, and the return-value statement is relevant. Minor redundancy exists between the first two sentences, but overall it is efficient.

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

Completeness3/5

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

For a three-parameter tool with no annotations and a 0% schema coverage, the description covers the core transformation and success return, but not parameter semantics or default behaviors. It is minimally viable for an agent to understand the operation, but gaps around range/worksheet usage and alternatives remain.

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?

Schema description coverage is 0%, so the description must compensate, but it only mentions 'range' and 'worksheet' generically. It does not explain the expected format of _range, whether worksheet is optional, or what happens when these parameters are null. file_uuid is required but never described.

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 states a specific verb and resource: removes all line break characters from text values in a worksheet range. It explicitly enumerates the handled characters (\n, \r\n, \r), which clearly differentiates it from siblings like remove_extra_line_breaks or trim_text.

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 usage context is clear: apply this when all line breaks must be removed from a specified range. However, it does not explicitly contrast itself with remove_extra_line_breaks or state when not to use it, leaving the alternative-selection logic mostly implicit.

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

Deploy Server