# Search TeamBoost tasks by meaning

Illustrative planning brief; no automatic product import.

Illustrative request: find tasks related to confusing login behavior, even when their titles use different wording.

## Decision

Use tb_search_tasks for topical discovery, then inspect references and limitations before answering.

## Owned work

- Define the topic
  - Owner role: User
  - Acceptance evidence: The request expresses the behavior or concept being investigated.
- Inspect returned matches
  - Owner role: Agent
  - Acceptance evidence: Each selected result is relevant to that topic and carries usable references.
- State the coverage
  - Owner role: Reviewer
  - Acceptance evidence: The answer labels semantic matches and acknowledges indexing gaps.

## Workflow

1. Phrase the actual topic instead of a guessed status filter.
2. Inspect returned relevance rather than accepting every match.
3. Use structured filtering when the question requires exact attributes.

## Judgment

Source documentation notes that recently created tasks can be absent until embeddings are available.


## Illustrative search intent

Topic: confusing login behavior.
Result interpretation: relevant matches, not exhaustive coverage.
Next action: inspect task detail or use an exact filter when a precise set is required.


## Before / after

Before: Call a topic-search result “all completed tasks owned by the requester.”

After: Use semantic search for relevant topic matches and structured filtering for exact status/owner constraints.


## Workflow questions

### Does semantic search return all matching tasks?

No. Treat it as topical discovery, not an exhaustive exact-attribute result.

### Which tool handles exact status or owner constraints?

The source exposes tb_list_tasks for structured task filtering.

## Product connection

The TeamBoost MCP example retrieves work by meaning; review ranked results without claiming an exhaustive inventory.

Confirm account availability before adopting this manual outline.