Skip to main content
Glama

search_advanced

Search tasks using multiple optional filters combined with AND logic. Use for GTD reviews, area sweeps, or finding modified tasks.

Instructions

Multi-predicate search. Every filter is optional and AND-combined.

Use this for GTD reviews ("what's overdue?"), area sweeps, or finding tasks modified recently.

Args: status: 'pending', 'cancelled', or 'completed'. type: 'task', 'project', or 'heading'. schedule: 'inbox', 'anytime', or 'someday'. area_uuid: Filter by area. project_uuid: Filter by parent project. tag: Tag UUID or name to filter by. include_descendants: When tag is set, also match descendant tags. start_date_from, start_date_to: Unix-timestamp range for start date. deadline_from, deadline_to: Unix-timestamp range for deadline. modified_since: Only tasks modified at or after this timestamp. completed_since: Only tasks completed at or after this timestamp. include_trashed: If True, also include trashed tasks. limit: Optional max number of tasks. offset: Optional pagination offset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
typeNo
scheduleNo
area_uuidNo
project_uuidNo
tagNo
include_descendantsNo
start_date_fromNo
start_date_toNo
deadline_fromNo
deadline_toNo
modified_sinceNo
completed_sinceNo
include_trashedNo
limitNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided; description discloses that filters are AND-combined and covers all parameters with behavioral details (e.g., include_trashed, include_descendants). Missing pagination or return format details.

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 front-loaded with purpose and usage tips, but the parameter list could be slightly more compact. Overall well-structured.

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?

Given 16 optional parameters and existing output schema, the description covers all necessary behavioral details including filter combination, parameter range, and usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description fully compensates by explaining every parameter's meaning, accepted values, and defaults, adding significant value beyond the schema types.

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 it is a multi-predicate search with AND-combined optional filters. It explicitly contrasts with simpler listing tools, making the purpose unambiguous.

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

Usage Guidelines4/5

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

The description lists specific use cases (GTD reviews, area sweeps, finding recently modified tasks) but does not explicitly mention when not to use or alternatives.

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/nkootstra/things'

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