Unified.to MCP Server

List issues

list_unified_issues

Read-onlyIdempotent

List issues from the connected account. Returns an array of issue records. Supports filtering by updated_gte, sort, order, and pagination. Use to browse or search many issues; to fetch a single issue by its ID, use get_unified_issue.

Input Schema

Name	Required	Description
`sort`	No
`limit`	No	Maximum number of results to return in one page (default 100). Use together with 'offset' to page through large result sets.
`order`	No
`offset`	No	Number of results to skip, for pagination (default 0). Advance by 'limit' each page to fetch subsequent results.
`updated_gte`	No	Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)

Output Schema

Name	Required	Description	Default
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results to return in one page (default 100)"New value: +"Maximum number of results to return in one page (default 100). Use together with 'offset' to page through large result sets."

changedInput schema / properties / offset / description

Previous value: -"Number of results to skip, for pagination (default 0)"New value: +"Number of results to skip, for pagination (default 0). Advance by 'limit' each page to fetch subsequent results."

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Issue": {
+      "properties": {
+        "created_at": {
+          "description": "(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "customer_note": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "importance": {
+          "description": "1-5, 1 is lowest",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "resolution_time": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "size": {
+          "description": "1-5, 1 is lowest",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "One of: COMPLETED, NEW, ROADMAP, IN_PROGRESS, ON_HOLD, VALIDATING, REJECTED",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ticket_ref": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "title": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": {
+          "anyOf": [
+            {
+              "$ref": "#/$defs/Issue_type"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "updated_at": {
+          "description": "(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "workspace_id": {
+          "description": "(reference to KmsSpace)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "Issue_type": {
+      "items": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "results": {
+      "items": {
+        "anyOf": [
+          {
+            "$ref": "#/$defs/Issue"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 24, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum number of results to return in one page (default 100)"

addedInput schema / properties / offset / description

Added value: +"Number of results to skip, for pagination (default 0)"

Changed2 schema fields changedMay 7, 2026

removedInput schema / properties / fields

Removed value: -{
-  "description": "Comma-separated list of fields to include in the response",
-  "type": "string"
-}

changedInput schema / properties / updated_gte / description

Previous value: -"Return only results whose updated date is equal or greater to this value"New value: +"Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)"

First observedFeb 19, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile needs no restating. The description adds the return shape ('array of issue records') and confirms which filter axes exist, but says nothing about rate limits, result caps, or default page size behavior beyond what the schema documents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose, return shape, capabilities, then the sibling routing. The disambiguation is front-loaded and nothing is redundant.

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?

With an output schema present, return values need no elaboration, and the description covers purpose, filters, pagination, and the alternative tool. Minor gap: it doesn't hint at default limit/offset or total-count semantics, which matters for a paginated list.

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 coverage is only 60% (sort and order have enums but no descriptions), and the description compensates by naming all four filter/pagination axes (updated_gte, sort, order, pagination). It confirms the supported filter set but adds no format or default details beyond the schema entries.

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 (issues), gives the scope (from the connected account), and names the sibling it is not (get_unified_issue). An agent can distinguish it from the 30+ siblings without opening a schema.

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?

Explicitly says when to use it ('to browse or search many issues') and routes to the alternative for the single-record case ('to fetch a single issue by its ID, use `get_unified_issue`'). Clear when-to-use plus a named alternative.

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

All Unified.to MCP Server tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?