Cloudlabels

Rename sheet

rename_sheet

Destructive

Rename a sheet in this organization. Pass sheet_id or sheet_number plus name. Shopify store sheets cannot be renamed here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`sheet_id`	No
`sheet_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare that this is a non-read-only, destructive, non-idempotent operation. The description adds the useful Shopify-sheet exclusion, but does not explain what makes the operation destructive, whether the old name is recoverable, permission requirements, or error behavior.

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?

The description is two sentences, front-loaded with the action, and contains no wasted language. The identifier guidance follows immediately, making the definition easy to scan.

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 a simple three-parameter mutation, the description covers purpose, identifier selection, and a key exclusion. Annotations carry the safety profile and the schema carries constraints, though some behavioral detail around the destructive hint remains implicit.

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

Parameters3/5

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

With 0% schema description coverage, the description partially compensates by naming all three parameters and explaining that sheet_id or sheet_number is passed alongside name. However, it omits parameter constraints such as name length, sheet_number range, sheet_id format, and whether both identifiers may be supplied.

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: "Rename a sheet in this organization." It also scopes the operation and explicitly excludes Shopify store sheets, which helps distinguish it from sibling sheet and column operations such as rename_columns.

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?

It gives clear invocation guidance: pass sheet_id or sheet_number plus name. It also gives a when-not condition by stating Shopify store sheets cannot be renamed here, though it does not name an alternative path for that excluded case.

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?