Skip to main content
Glama

Coline

Change a protected range

update_sheet_protection
Idempotent

Changes a protected range's name, cells, mode or allowed people.

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": {
      "workspace": "<workspace>",
      "sheetId": "<sheetId>",
      "protectionId": "<protectionId>"
    },
    "name": "update_sheet_protection"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
nameNo
rowIdsNo
sheetIdYesSheet id from search, fetch or create_sheet.
fieldIdsNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
descriptionNo
allowUserIdsNo
protectionIdYes

Output Schema

NameRequiredDescriptionDefault
protectionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so safety is covered; the description adds nothing beyond that. For a 9-parameter mutation it stays silent on the questions that matter: whether array fields (rowIds, fieldIds, allowUserIds) replace the whole set or merge, whether passing null description clears it, and whether unspecified fields are left untouched.

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?

A single front-loaded sentence with no filler, so there is nothing to trim. Its brevity is the source of the gaps rather than verbosity, which is a separate dimension.

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

Completeness2/5

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

The presence of an output schema removes the need to document return values, but a mutation tool with 9 parameters at 22% schema coverage needs much more than one sentence. Missing are partial-update semantics, list-replacement behavior, and any routing away from the create/delete siblings.

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?

Schema description coverage is only 22%, so the description should compensate, and it partially does by mapping conceptual facets ("cells", "allowed people") to parameters like rowIds/fieldIds and allowUserIds. However, the four listed facets are largely restatements of parameter names, and nothing explains protectionId, workspace, or the replacement semantics of the array parameters.

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?

The description states a specific verb ("changes") plus the resource ("a protected range") and enumerates the mutable facets: name, cells, mode, allowed people. That is enough to distinguish it from a create tool, but it does not name or differentiate from siblings such as protect_sheet_range or delete_sheet_protection, leaving the create/update/delete boundary to be inferred.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no statement that this only applies to an already-existing protection, and no pointer to protect_sheet_range for creating one or delete_sheet_protection for removing one. Usage is only implied by the word "changes".

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources