Skip to main content
Glama

Coline

Change a task view

update_task_view
Destructive

Renames a view or changes its filters, plain-language filter, layout, scope or who sees it (owner or admin only).

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>",
      "viewId": "<viewId>"
    },
    "name": "update_task_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
queryNo
scopeNo
layoutNo
viewIdYes
sentenceNoA plain-language filter, e.g. "anything a customer is waiting on".
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
visibilityNo

Output Schema

NameRequiredDescriptionDefault
viewYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

The description adds the owner/admin authorization requirement, genuine value beyond the annotations, which only flag destructiveHint=true and idempotentHint=false. Critically, it does not disclose the destructive semantics: whether supplying a partially populated 'query' replaces the entire existing filter tree or merges with it, and whether omitted properties are wiped. For a tool the annotations mark destructive, that omission is a real gap.

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 dense sentence with the enumerable capabilities front-loaded and the permission constraint following in parentheses. There is no filler, though the long comma list makes it slightly harder to scan than a two-clause structure would.

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?

The tool is complex (8 parameters, deeply nested object schema, destructive and non-idempotent) and an output schema exists, so return values need not be explained. The description still leaves the replace-vs-merge semantics of 'query' and 'scope' unresolved, which is the main thing an agent must know before calling a destructive update.

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?

Schema description coverage is only 25%, so the description must carry weight, and it does: it maps prose to six of the eight parameters (name, filters, the plain-language 'sentence', layout, scope, visibility). It adds the useful gloss that 'sentence' is a plain-language filter. It says nothing about the required workspace/viewId pair or about the deeply nested filter sub-fields, so it stops short of full compensation.

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 names a specific resource (a task view) and enumerates the modifiable aspects: name, filters, plain-language filter, layout, scope, and visibility. An agent immediately knows this is a mutation of an existing view rather than creation or deletion. It does not explicitly differentiate itself from siblings like build_task_view_layout or create_task_view, which keeps it just below a 5.

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 parenthetical '(owner or admin only)' supplies a real prerequisite for invocation, which is useful context. However, there is no guidance on when to choose this over create_task_view, build_task_view_layout, or delete_task_view, and no statement that the view must already exist. Usage is implied rather than directed.

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