Cloudlabels

Update sheet settings

update_sheet_settings

Destructive

Update display settings for one sheet, or show and hide columns. Pass sheet_id or sheet_number. Display keys: hide_empty_columns, wrap_text, wrap_header_text, table_compactness (compact, normal, or plus), show_images, image_field, image_field_fallback, export_all_columns. To show or hide columns, pass columns: [{ column, visible }]. column is a column id (such as data3) or the header name. The value is trimmed and matched case-insensitively. A column id wins when it matches. If several columns share a header name, pass the column id. Optional value_kind is text, currency, ean13_body, ean8_body, upca_body, or upce_body. Optional currency_code is three uppercase letters (ISO 4217), for example NOK. An empty currency_code clears the code. A code without value_kind sets the column to currency. Names, order, width, and image_field stay as stored. Existing cell values are not converted. Shopify store sheets are refused. Hiding a catalog variant axis column is refused. An unknown column, a shared header name, two different visible values, or two different currency settings for the same column returns an error and nothing is saved.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_sheet_settings"
  }
}

Input Schema

Name	Required	Description	Default
`columns`	No
`sheet_id`	No
`wrap_text`	No
`image_field`	No
`show_images`	No
`sheet_number`	No
`wrap_header_text`	No
`table_compactness`	No
`export_all_columns`	No
`hide_empty_columns`	No
`image_field_fallback`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing refusal conditions ("Shopify store sheets are refused", "Hiding a catalog variant axis column is refused"), atomicity ("returns an error and nothing is saved"), and non-effects ("Existing cell values are not converted", "Names, order, width, and image_field stay as stored"). These are exactly the side-effect boundaries an agent needs for a destructiveHint=true mutation.

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?

Dense and front-loaded: the operating modes come first, then column semantics, then refusal/error rules. Some sentences merely restate schema enums (table_compactness, value_kind), which is mild duplication, but the remaining text is almost entirely load-bearing.

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?

For an 11-parameter, zero-coverage mutation tool with no output schema, the description covers identification, column matching, value typing, and failure modes. The residual gap is the meaning of a few boolean display flags, which an agent can only guess at.

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?

With 0% schema description coverage the description carries the full load and mostly succeeds: it explains the columns array shape, id-vs-header matching rules, case-insensitive trimming, ambiguity handling, value_kind enum values, and currency_code format/clearing behavior. Several display keys (image_field_fallback, export_all_columns, hide_empty_columns) are only listed by name without semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Update display settings for one sheet, or show and hide columns") and scopes it away from adjacent operations by noting that "Names, order, width, and image_field stay as stored," which separates it from rename_columns/remove_column. It never names a sibling directly, so an agent must infer the boundary.

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 tells how to address the sheet ("Pass sheet_id or sheet_number") and what the two operating modes are, but gives no explicit guidance on when to prefer this tool over get_sheet_settings or the dedicated column tools. Usage is implied rather than stated.

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

All Cloudlabels tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?