Skip to main content
Glama

find_tasks

Read-only

Search every task across all projects, including others' work, to answer who's doing what, what's overdue, or where a card went. Filter by assignee, label, status, text, and more.

Instructions

Search tasks across every project you can see - including other people's.

Unlike list_actionable_tasks, which is your own ready-to-work queue, this answers questions about the whole workspace: what is Ada working on, what is overdue, where did that card about the login bug go.

Searching for a person finds all three ways work reaches them: tasks they are assigned to, tasks holding a checklist item assigned to them, and tasks where they were mentioned in a comment. Each result says which, in matched_by, and carries the specific checklist items and mentions. Results are read-only context; claiming and editing still go through the usual tools, and other people's tasks remain off limits to edit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoCase-insensitive text to look for in the title or description.
labelNoOnly tasks carrying this label, e.g. 'priority: high'.
limitNoMaximum results (1-100).
statusNoRestrict to todo, in_progress, review or done. Default: every stage except done.
assigneeNoWhose work to show: a name, email or id; 'me'; 'anyone'; or 'unassigned'. Defaults to anyone.
board_idNoSearch every project inside one board (container).
project_idNoSearch one project (tab) instead of all of them.
include_doneNoInclude finished work. Off by default.
overdue_onlyNoOnly tasks whose due date has passed.
include_mentionsNoWhen searching for a person, also return tasks where they were mentioned in a comment. On by default.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations note readOnlyHint and openWorldHint, but the description adds substantial behavior: search matches tasks, checklist items, and mentions for a person; results include matched_by; results are read-only context; other people's tasks are off-limits for edit. No contradiction with annotations.

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?

Four sentences are front-loaded with the core purpose, then differentiation, then detail. No wasted words; each sentence adds value and the structure is logical.

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?

With full schema coverage, annotations, and an output schema present, the description covers the high-level scope, sibling differentiation, and key behavioral nuances. Nothing essential is missing for a search tool of this complexity.

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 covers all 10 parameters with descriptions, so baseline is 3. The description adds meaningful semantics for the assignee parameter, explaining the three ways a person can be matched and that results indicate how via matched_by. This goes beyond schema.

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 clearly states the tool searches tasks across all visible projects, including others' tasks. It explicitly distinguishes itself from list_actionable_tasks, naming the sibling tool and its different scope.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: use for whole-workspace questions versus list_actionable_tasks for your own queue. Also explains read-only nature and that edits go through other tools, with a clear exclusion for editing others' tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KT-SPARKS/planka-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server