Skip to main content
Glama

Coline

Make a task view

create_task_view

Saves a view: which tasks (filters and an optional plain-language filter), from where (some boards, all boards, a project or a cycle) and how (layout, grouping, sorting).

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>",
      "name": "<name>",
      "scope": "<scope>"
    },
    "name": "create_task_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
queryNo
scopeYes
homeIdNo
layoutNo
homeKindNoShow it as a tab on this board, project or cycle.
sentenceNoA plain-language filter, e.g. "anything a customer is waiting on".
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
visibilityNopersonal (default) or workspace.

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?

Beyond the non-read-only and non-destructive annotations, “Saves a view” usefully indicates that a view definition, rather than task data, is persisted. It adds no further context about default visibility, home-tab placement, or how the plain-language filter behaves alongside structured filters.

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?

A single front-loaded sentence moves directly from the persisted result to three well-organized configuration dimensions. The parenthetical lists are dense but directly relevant, with no filler or repetition.

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?

Together with the detailed input schema, annotations, and output schema, the description is sufficient to understand the basic creation operation without needing return-value documentation. For such a nested tool, however, the lack of sibling-selection guidance and key interaction or default behavior leaves noticeable gaps.

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?

The description usefully organizes a complex invocation into task filters, four scope choices, and layout/grouping/sorting, partially compensating for the 44% schema description coverage. However, much of this restates property names and enums, and it adds no detail on date formats, filter combination, sentence precedence, or less intuitive parameters such as homeId.

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?

“Saves a view” gives a concrete persistence-oriented verb and resource, while “which tasks,” “from where,” and “how” define the saved task selection, scope, and presentation. It is clear that this is not merely a task search, but it does not explicitly distinguish creation from build_task_view_layout or update_task_view.

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 implies use when an agent wants to persist a filtered, scoped, formatted task view. It provides no explicit when/when-not guidance, prerequisites, or alternatives for other view operations such as building a layout or updating an existing view.

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