Skip to main content
The server exposes ten tools. All of them are reads - none creates, changes, or deletes anything. You do not need to call these by name. Describe what you want and the assistant picks; the list is here so you know what is reachable.

Projects and runs

Tests

Failures and history

Workspaces

ListWorkspaces has no API equivalent - the REST API is always scoped to the single workspace in the request URL.

Arguments every tool accepts

Tools that return lists also take page and page_size. GetProjectInsights is not paginated; it takes start_date, end_date, and timezone instead, covers the most recent 3 months, and refuses an older start_date rather than clamping it. Identifiers are the short alphanumeric segments of a NeetoPlaydash admin URL: in https://acme.neetoplaydash.com/admin/projects/pdqmxlz/runs/kftwnab/test_entities/vhrscje, pdqmxlz is the project_id, kftwnab the run_id, and vhrscje the test_entity_id.

Response format

Every tool returns the same payload twice: as TOON in the text content and as JSON in structuredContent. TOON is a compact tabular encoding - a header such as projects[3]{id,name,archived}: means the next three lines are comma-separated rows with those fields in that order. Both carry identical data; read whichever your client exposes.
Artifact and trace URLs are time-limited links to files stored by NeetoPlaydash. Opening a trace link sends that URL to Playwright’s hosted viewer at trace.playwright.dev, which is operated by Microsoft, not by NeetoPlaydash.