YouGile MCP

Yougile Find Tasks

yougile_find_tasks

Read-only

Search tasks by project, board, column, assignee, or title keywords, with filters for status, overdue, and completion dates to locate specific work items.

Instructions

Find tasks by project/board/column names, assignee and title words. Without a place, searches the workspace's default project if one is set, else the whole company. Completed tasks show completed_at; tasks in a column that counts as done but not marked completed show done_by_column: true (YouGile keeps no date for those); open tasks past their deadline show overdue: true. completed_since/completed_until select tasks completed in a period, newest first.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	No	Words from the title, or a task number
`board`	No	Board name or "Project / Board"
`limit`	No
`column`	No	Column name (needs a board or default)
`status`	No	Default "open", or "any" when a column is given
`project`	No	Project name
`assignee`	No	Name, email or "me"
`completed_since`	No	Only tasks completed on or after this date (implies completed)
`completed_until`	No	Only tasks completed on or before this date (implies completed)
`include_archived`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Sep 24, 2026

addedInput schema / properties / completed_since

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only tasks completed on or after this date (implies completed)"
+}

addedInput schema / properties / completed_until

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only tasks completed on or before this date (implies completed)"
+}

First observedv0.1.0Sep 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description enriches that with concrete behavioral detail: completed tasks expose completed_at, column-done tasks expose done_by_column: true with no date, overdue open tasks expose overdue: true, and completed-since/until results are ordered newest first. This goes beyond the annotation and helps the agent interpret returned data correctly.

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 a compact paragraph with no filler. It front-loads the core purpose, then efficiently explains search scope and output flags, with each sentence contributing meaningful behavioral or filtering information.

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

Completeness5/5

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

For a read-only search tool with no output schema, the description covers the important return quirks (completed_at, done_by_column, overdue), default workspace behavior, and the semantics of the completed-period filters. This is sufficient for an agent to invoke the tool and interpret results without additional context.

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 coverage is 80%, so the baseline is 3, but the description adds value by explaining the default project/whole-company scope and how completed_since/completed_until select tasks in a period. Schema descriptions already handle most parameters, so the description's extra context lifts it above baseline without fully replacing schema detail.

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 opens with a specific verb and resource: 'Find tasks by project/board/column names, assignee and title words.' This immediately distinguishes it from broader sibling tools like yougile_tasks by focusing on search criteria rather than plain listing. It also communicates the scope behavior (default project or whole company), which sharpens the resource being searched.

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 the tool is for filtered searching, and it explains what happens when no place is specified. However, it never explicitly names sibling alternatives like yougile_tasks or states when NOT to use this tool, so the agent must infer usage from the filter-oriented wording.

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

Yougile Find Tasks

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools