Uxia

List Insights

list_insights

Read-onlyIdempotent

List findings ranked by severity. Omit blockId for top insights across all AI task blocks; limit applies globally. Supply blockId for one task. Keep returned block/run IDs with evidence. One call includes all severities; do not iterate per severity or category. Use severity/category filters only when requested. testerName filters AI-tester evidence by name; use list_transcripts for names and get_human_session for human participants. Use IDs from list_test_blocks to target a block/run; omission uses the documented defaults. Legacy tests also supported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "testId": "<testId>"
    },
    "name": "list_insights"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`runId`	No
`sortBy`	No		severity
`testId`	Yes
`blockId`	No	Select one block from list_test_blocks. Omit to infer a sole relevant block; list_insights defaults to all AI blocks. Omit for legacy tests.
`category`	No
`severity`	No
`testerName`	No

Output Schema

Name	Required	Description	Default
`data`	No
`retry`	No
`runId`	No
`scope`	No
`total`	No
`status`	No
`testId`	No
`blockId`	No
`message`	No
`paywall`	No
`insights`	No
`nextStep`	No
`totalTesters`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedSep 30, 2026

removedOutput schema / properties / data / properties / insights / $ref
```
Removed value: -"#/properties/insights"
```

addedOutput schema / properties / data / properties / insights / items

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "category": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "evidenceCount": {
+      "type": "integer"
+    },
+    "frames": {
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    "ref": {
+      "type": "string"
+    },
+    "reporterCount": {
+      "type": "integer"
+    },
+    "severity": {
+      "enum": [
+        "high",
+        "medium",
+        "low",
+        "prototype",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "testerSeeds": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ref",
+    "title",
+    "severity",
+    "category",
+    "summary",
+    "reporterCount",
+    "evidenceCount",
+    "testerSeeds",
+    "frames"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / insights / type
```
Added value: +"array"
```
removedOutput schema / properties / data / properties / paywall / $ref
```
Removed value: -"#/properties/paywall"
```
addedOutput schema / properties / data / properties / paywall / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / data / properties / paywall / properties

Added value: +{
+  "feature": {
+    "type": "string"
+  },
+  "hiddenCount": {
+    "type": "integer"
+  }
+}

addedOutput schema / properties / data / properties / paywall / required
```
Added value: +[
+  "hiddenCount",
+  "feature"
+]
```
addedOutput schema / properties / data / properties / paywall / type
```
Added value: +"object"
```
removedOutput schema / properties / data / properties / total / $ref
```
Removed value: -"#/properties/total"
```
addedOutput schema / properties / data / properties / total / type
```
Added value: +"integer"
```
removedOutput schema / properties / data / properties / totalTesters / $ref
```
Removed value: -"#/properties/totalTesters"
```
addedOutput schema / properties / data / properties / totalTesters / type
```
Added value: +"integer"
```
removedOutput schema / properties / retry / properties / arguments / $ref
```
Removed value: -"#/properties/nextStep/properties/arguments"
```
addedOutput schema / properties / retry / properties / arguments / additionalProperties
```
Added value: +{}
```
addedOutput schema / properties / retry / properties / arguments / type
```
Added value: +"object"
```

First observedSep 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds important behavioral context: limit is global when blockId is omitted, returned block/run IDs should be kept with evidence, and legacy tests are supported. There is no contradiction with annotations.

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-loads purpose, then layers usage constraints and resolver guidance. It is dense but every sentence provides an actionable instruction, aside from the brief legacy-tests note which remains useful context.

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

Completeness3/5

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

Output schema exists, so return values need not be explained, and annotations cover safety. However, for an 8-parameter tool with low schema description coverage, omitting required testId semantics and sortBy behavior leaves meaningful gaps.

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

Parameters3/5

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

Schema description coverage is only 13%, so the description must carry the load. It explains blockId omission/supply, global limit behavior, severity/category filter usage, and testerName scope, but does not explain sortBy (severity vs relevance), the required testId meaning, or the runId format.

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 'List' and resource 'findings/insights', plus the ranking basis 'by severity'. It distinguishes from the singular sibling get_insight by describing a multi-item listing over AI task blocks.

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

Usage Guidelines5/5

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

Gives explicit when-to-use rules: omit blockId for all AI blocks, supply blockId for one task, one call includes all severities, do not iterate per severity/category, and use filters only when requested. It also names list_transcripts and get_human_session as alternatives for name resolution.

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

All Uxia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?