Tideways MCP Server

List issues

tideways_list_issues

Read-onlyIdempotent

List a project's errors, slow SQL, deprecations, warnings, or notices, newest first, to identify failures or slow queries and how often they occur.

Instructions

List error, slow-SQL, deprecation, warning or notice issues of a project, newest occurrence first, 10 per page, with the total count. Use to find what is failing or slow and how often. Reads all services unless "service" is passed or configured; "transactionIds" narrows to issues of given transactions. One type and one status per call. There is no time filter; use lastOccurred to judge recency.

Input Schema

Name	Required	Description	Default
`page`	No	Page number; 10 issues per page
`type`	No	error = exceptions and fatal errors, slowsql = slow SQL queries, deprecated = deprecations, warning = PHP warnings, notice = PHP notices	error
`detail`	No	"concise" (default) returns a trimmed summary. "full" also includes the unmodified API response under "raw"; it can be very large.	concise
`status`	No	open (default) = unresolved; all = open and ignored together; resolved, ignored and not_error are triaged states; "new" currently returns the same list as "open".	open
`project`	No	Tideways project as "project" or "organization/project". Defaults to the defaultProject that tideways_list_projects reports; call it for valid names.
`service`	No	Service, e.g. "web" or "worker". Defaults to the configured service, else all services of the project; tideways_list_services lists them.
`environment`	No	Environment, e.g. "production" or "staging". Defaults to the configured environment, else production; criteria.environment (traces: each trace's environment) shows which was used. When results come back, an unknown name fails with an error.
`transactionIds`	No	Only issues raised in these transactions: numeric IDs from transactions[].id of tideways_get_performance.

Output Schema

Name	Required	Description
`raw`	No	Unmodified Tideways API response; present only when detail is "full".
`issues`	Yes
`hasMore`	Yes	True when later pages exist; request the next page for more
`project`	Yes
`criteria`	Yes
`totalItems`	Yes	Issues matching the filters on all pages
`totalPages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed27 schema fields changedv2.1.1Oct 15, 2026

addedInput schema / properties / service

Added value: +{
+  "description": "Service, e.g. \"web\" or \"worker\". Defaults to the configured service, else all services of the project; tideways_list_services lists them.",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / status / description

Previous value: -"open (default) = unresolved; resolved, ignored and not_error are triaged states; \"new\" currently returns the same list as \"open\". There is no \"all\"; call once per status you need."New value: +"open (default) = unresolved; all = open and ignored together; resolved, ignored and not_error are triaged states; \"new\" currently returns the same list as \"open\"."

changedInput schema / properties / status / enum

Previous value: -[
-  "open",
-  "new",
-  "resolved",
-  "not_error",
-  "ignored"
-]New value: +[
+  "open",
+  "all",
+  "new",
+  "resolved",
+  "not_error",
+  "ignored"
+]

addedInput schema / properties / transactionIds

Added value: +{
+  "description": "Only issues raised in these transactions: numeric IDs from transactions[].id of tideways_get_performance.",
+  "items": {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / properties / type / description

Previous value: -"error = exceptions and fatal errors, slowsql = slow SQL queries, deprecated = deprecations"New value: +"error = exceptions and fatal errors, slowsql = slow SQL queries, deprecated = deprecations, warning = PHP warnings, notice = PHP notices"

changedInput schema / properties / type / enum

Previous value: -[
-  "error",
-  "slowsql",
-  "deprecated"
-]New value: +[
+  "error",
+  "slowsql",
+  "deprecated",
+  "warning",
+  "notice"
+]

addedOutput schema / properties / criteria / properties / service / description
```
Added value: +"Service whose issues were read; null = all services"
```

changedOutput schema / properties / criteria / properties / type / enum

Previous value: -[
-  "error",
-  "slowsql",
-  "deprecated"
-]New value: +[
+  "error",
+  "slowsql",
+  "deprecated",
+  "warning",
+  "notice"
+]

changedOutput schema / properties / hasMore / description

Previous value: -"True when the page is full; request the next page for more. The API reports no total."New value: +"True when later pages exist; request the next page for more"

addedOutput schema / properties / issues / items / properties / durationMs

Added value: +{
+  "description": "Slow SQL queries: duration of the query in ms; null for other types",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / issues / items / properties / firstOccurred / anyOf

Added value: +[
+  {
+    "description": "\"YYYY-MM-DD HH:mm\"",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / issues / items / properties / firstOccurred / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / issues / items / properties / lastOccurred / anyOf

Added value: +[
+  {
+    "description": "\"YYYY-MM-DD HH:mm\"",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / issues / items / properties / lastOccurred / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedOutput schema / properties / issues / items / properties / originatingFunction / description
```
Added value: +"Always null; source names the code"
```

changedOutput schema / properties / issues / items / properties / topFrame / description

Previous value: -"Innermost stack frame of the last occurrence"New value: +"Always null: tideways_get_issue returns the stack trace; source names the file and line"

addedOutput schema / properties / issues / items / properties / transactionCount / description
```
Added value: +"Always null: tideways_get_issue returns the affected transactions"
```
changedOutput schema / properties / issues / items / properties / transactionCount / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

addedOutput schema / properties / issues / items / properties / transactions / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / issues / items / properties / transactions / description

Previous value: -"First 5 of transactionCount affected transactions, in no particular order; detail \"full\" lists all (large)"New value: +"Always null: tideways_get_issue returns the affected transactions with counts; filter the list by transaction with \"transactionIds\""

removedOutput schema / properties / issues / items / properties / transactions / items
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / issues / items / properties / transactions / type
```
Removed value: -"array"
```
addedOutput schema / properties / issues / items / properties / type / description
```
Added value: +"The requested type; tideways_get_issue takes it with the id"
```

changedOutput schema / properties / issues / items / required

Previous value: -[
-  "id",
-  "type",
-  "title",
-  "message",
-  "source",
-  "originatingFunction",
-  "status",
-  "occurrences",
-  "occurrencesSinceLastRelease",
-  "firstOccurred",
-  "lastOccurred",
-  "environments",
-  "services",
-  "transactionCount",
-  "transactions",
-  "topFrame"
-]New value: +[
+  "id",
+  "type",
+  "title",
+  "message",
+  "source",
+  "originatingFunction",
+  "status",
+  "occurrences",
+  "occurrencesSinceLastRelease",
+  "firstOccurred",
+  "lastOccurred",
+  "environments",
+  "services",
+  "durationMs",
+  "transactionCount",
+  "transactions",
+  "topFrame"
+]

addedOutput schema / properties / totalItems

Added value: +{
+  "description": "Issues matching the filters on all pages",
+  "type": "number"
+}

addedOutput schema / properties / totalPages
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "project",
-  "criteria",
-  "issues",
-  "hasMore"
-]New value: +[
+  "project",
+  "criteria",
+  "issues",
+  "hasMore",
+  "totalItems",
+  "totalPages"
+]

First observedv2.0.0Oct 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavior: 10-per-page paging with a total count, newest-first ordering, one type and one status per call, no time filtering, and how service/environment defaults resolve. It omits return-shape and error/pagination-failure behavior, so not a 5.

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?

Front-loaded with purpose, sorting and page size before the scoping caveats; dense but nearly every clause carries information. Slightly sentence-heavy with several defaults packed into one paragraph.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and the description covers scope, defaults and filtering adequately. The only gap is that it never points to tideways_get_issue for per-issue detail, which matters given nine siblings.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3, but the description contributes beyond it: the single-type/single-status-per-call constraint and the default-resolution rules for service and environment. It largely parallels what the schema already documents for page, type, status, detail and transactionIds.

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?

States a specific verb and resource (list issues of a project) with scope details: the five issue types, sort order (newest occurrence first), page size (10) and total count. This is clearly distinguishable from the singular sibling tideways_get_issue.

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?

"Use to find what is failing or slow and how often" gives an explicit context, and the description routes the agent (tideways_list_projects for valid names, tideways_list_services for services) plus notes there is no time filter and to use lastOccurred for recency. It does not name tideways_get_issue as the alternative for drilling into one issue, so it stops short of full when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server