Trunk MCP tool: Search Test

Overview

The search-test tool looks up a test by part of its name, class, or file. It searches the repository’s tests and, if your organization uses test collections, the repository’s tests in every collection. Return Type: Metadata about each matching test, including its ID and status. Results from test collections are listed in their own section, with the test’s ID, its Collection ID, and whether it is quarantined.

Parameters

Required Parameters

Parameter	Type	Description
`repoName`	string	Repository name in `owner/repo` format (e.g., `trunk-io/trunk`)
`testNameSearch`	string	Case-insensitive part of the test’s name, class, or file

Optional Parameters

Parameter	Type	Description
`orgSlug`	string	The name of your organization in the Trunk app
`testCollectionShortId`	string	The Collection ID of one test collection to search. Get it from `list-test-collections`. Omit to search every collection
`limit`	number	Maximum number of results to return, up to 20, from the repository and again from its test collections. Defaults to 5

Which tests are searched

What the tool searches follows your organization’s migration to test collections, and matches what the Trunk app shows you:

Organization	Searched
Not using test collections	The repository’s tests
Migrating to test collections	The repository’s tests and its tests in every collection. The same test can appear in both lists
Fully on test collections	The repository’s tests in every collection

Passing testCollectionShortId searches only that collection.

Getting Parameter Values

If your AI assistant doesn’t have direct access to Git information, use these commands: Get repository name:

git remote -v

Look for the repository name in the output (e.g., trunk-io/trunk from git@github.com:trunk-io/trunk.git)

Usage Examples

Search

What's the test case ID for the test "clear all filters button appears in empty state and clears filters"

Search one test collection

Find the "checkout" tests in the backend-unit test collection

Error Handling

Error	Cause	Resolution
`No tests matched {searchString} in {repoName}`	No results found	Check your search string and try again
`No tests matched {searchString} in {repoName} in test collection {collectionId}`	No results in that collection, or no collection with that ID in your organization	Check the Collection ID with `list-test-collections`
`Trunk could not read ... just now`	One of the places Trunk stores test results was unavailable, so results from it may be missing	Try again shortly
Repository authorization error	Insufficient permissions or invalid repo name	Verify repository name format and your access permissions

​Overview

​Parameters

​Required Parameters

​Optional Parameters

​Which tests are searched

​Getting Parameter Values

​Usage Examples

​Search

​Search one test collection

​Error Handling