Skip to main content
Glama

asana_search_tasks

Find tasks in an Asana workspace using advanced filters for assignee, project, due date, tags, custom fields, completion status, and more.

Instructions

Search tasks in a workspace with advanced filtering options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoText to search for in task names and descriptions
due_onNoISO 8601 date string or null
sort_byNoSort by: due_date, created_at, completed_at, likes, modified_atmodified_at
start_onNoISO 8601 date string or null
tags_allNoComma-separated list of tag IDs that must all match
tags_anyNoComma-separated list of tag IDs
tags_notNoComma-separated list of tag IDs to exclude
completedNoFilter for completed tasks
teams_anyNoComma-separated list of team IDs
workspaceYesThe workspace to search in
created_onNoISO 8601 date string or null
is_blockedNoFilter for tasks with incomplete dependencies
is_subtaskNoFilter for subtasks
opt_fieldsNoComma-separated list of optional fields to include
is_blockingNoFilter for incomplete tasks with dependents
modified_onNoISO 8601 date string or null
assignee_anyNoComma-separated list of user IDs
assignee_notNoComma-separated list of user IDs to exclude
completed_onNoISO 8601 date string or null
due_at_afterNoISO 8601 datetime string
due_on_afterNoISO 8601 date string
liked_by_notNoComma-separated list of user IDs to exclude
projects_allNoComma-separated list of project IDs that must all match
projects_anyNoComma-separated list of project IDs
projects_notNoComma-separated list of project IDs to exclude
sections_allNoComma-separated list of section IDs that must all match
sections_anyNoComma-separated list of section IDs
sections_notNoComma-separated list of section IDs to exclude
custom_fieldsNoObject containing custom field filters. Keys should be in the format "{gid}.{operation}" where operation can be: - {gid}.is_set: Boolean - For all custom field types, check if value is set - {gid}.value: String|Number|String(enum_option_gid) - Direct value match for Text, Number or Enum fields - {gid}.starts_with: String - For Text fields only, check if value starts with string - {gid}.ends_with: String - For Text fields only, check if value ends with string - {gid}.contains: String - For Text fields only, check if value contains string - {gid}.less_than: Number - For Number fields only, check if value is less than number - {gid}.greater_than: Number - For Number fields only, check if value is greater than number Example: { "12345.value": "high", "67890.contains": "urgent" }
due_at_beforeNoISO 8601 datetime string
due_on_beforeNoISO 8601 date string
followers_notNoComma-separated list of user IDs to exclude
created_by_anyNoComma-separated list of user IDs
created_by_notNoComma-separated list of user IDs to exclude
has_attachmentNoFilter for tasks with attachments
portfolios_anyNoComma-separated list of portfolio IDs
sort_ascendingNoSort in ascending order
start_on_afterNoISO 8601 date string
assigned_by_anyNoComma-separated list of user IDs
assigned_by_notNoComma-separated list of user IDs to exclude
start_on_beforeNoISO 8601 date string
created_at_afterNoISO 8601 datetime string
created_on_afterNoISO 8601 date string
resource_subtypeNoFilter by task subtype (e.g. milestone)
created_at_beforeNoISO 8601 datetime string
created_on_beforeNoISO 8601 date string
modified_at_afterNoISO 8601 datetime string
modified_on_afterNoISO 8601 date string
completed_at_afterNoISO 8601 datetime string
completed_on_afterNoISO 8601 date string
modified_at_beforeNoISO 8601 datetime string
modified_on_beforeNoISO 8601 date string
commented_on_by_notNoComma-separated list of user IDs to exclude
completed_at_beforeNoISO 8601 datetime string
completed_on_beforeNoISO 8601 date string
Behavior2/5

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. The verb 'search' implies a read-only operation, but the description does not mention pagination, result limits, return format, or any side effects. This is a significant gap for a tool with 55 parameters and no output schema.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core purpose. However, it lacks any structural elements (e.g., bullet points or usage notes) that might help navigate a tool with a very large parameter set.

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?

Given the tool's complexity (55 parameters, nested objects, no output schema, no annotations), the description is far from complete. It does not explain what results are returned, how pagination works, or any usage caveats. The schema covers parameter definitions, but the description does not help the agent understand the overall behavior or expected output.

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 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond the phrase 'advanced filtering options,' which is already evident from the extensive parameter list. It neither compensates for missing schema details nor adds context beyond what the schema provides.

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 uses a specific verb ('search'), a clear resource ('tasks'), and a scoping context ('in a workspace'). It distinguishes from sibling tools like asana_search_projects (which searches projects) and asana_get_multiple_tasks_by_gid (which retrieves tasks by known IDs) by emphasizing the search/filtering nature.

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?

The description provides no guidance on when to prefer this tool over alternatives, nor any exclusions or prerequisites. It only states the generic action of searching tasks with filters, leaving the agent to infer appropriate use cases from the parameter list.

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/katxuyu/asana-mcp'

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