Unified.to MCP Server

List available integrations

list_unified_integrations

Read-onlyIdempotent

List integrations from the connected account. Returns an array of integration records. Supports filtering by updated_gte, categories, summary, active, env, type, and pagination. Use to browse or search many integrations.

Input Schema

TableJSON Schema

Name	Required	Description
`env`	No
`type`	No	Filter the results for only this integration type
`limit`	No	Maximum number of results to return in one page (default 100)
`active`	No	Filter the results for only the workspace's active integrations
`offset`	No	Number of results to skip, for pagination (default 0)
`summary`	No
`categories`	No	Filter the results on these categories
`updated_gte`	No	(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)

Schema Changelog

Changes observed during successful MCP inspections.

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)"

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / categories / items / enum

Previous value: -[
-  "passthrough",
-  "hris",
-  "ats",
-  "auth",
-  "crm",
-  "enrich",
-  "martech",
-  "ticketing",
-  "uc",
-  "accounting",
-  "storage",
-  "commerce",
-  "payment",
-  "genai",
-  "messaging",
-  "kms",
-  "task",
-  "scim",
-  "lms",
-  "repo",
-  "metadata",
-  "calendar",
-  "verification",
-  "ads",
-  "analytics",
-  "forms",
-  "shipping",
-  "assessment",
-  "signing",
-  "clubs",
-  "datastore"
-]New value: +[
+  "passthrough",
+  "hris",
+  "ats",
+  "auth",
+  "crm",
+  "enrich",
+  "martech",
+  "ticketing",
+  "uc",
+  "accounting",
+  "storage",
+  "commerce",
+  "payment",
+  "genai",
+  "messaging",
+  "kms",
+  "task",
+  "scim",
+  "lms",
+  "repo",
+  "metadata",
+  "calendar",
+  "verification",
+  "ads",
+  "analytics",
+  "forms",
+  "shipping",
+  "assessment",
+  "signing",
+  "clubs",
+  "datastore",
+  "cdp"
+]

Changed1 schema field changedJul 16, 2026

changedInput schema / properties / categories / items / enum

Previous value: -[
-  "passthrough",
-  "hris",
-  "ats",
-  "auth",
-  "crm",
-  "enrich",
-  "martech",
-  "ticketing",
-  "uc",
-  "accounting",
-  "storage",
-  "commerce",
-  "payment",
-  "genai",
-  "messaging",
-  "kms",
-  "task",
-  "scim",
-  "lms",
-  "repo",
-  "metadata",
-  "calendar",
-  "verification",
-  "ads",
-  "forms",
-  "shipping",
-  "assessment"
-]New value: +[
+  "passthrough",
+  "hris",
+  "ats",
+  "auth",
+  "crm",
+  "enrich",
+  "martech",
+  "ticketing",
+  "uc",
+  "accounting",
+  "storage",
+  "commerce",
+  "payment",
+  "genai",
+  "messaging",
+  "kms",
+  "task",
+  "scim",
+  "lms",
+  "repo",
+  "metadata",
+  "calendar",
+  "verification",
+  "ads",
+  "analytics",
+  "forms",
+  "shipping",
+  "assessment",
+  "signing",
+  "clubs",
+  "datastore"
+]

Changed3 schema fields changedMay 7, 2026

changedInput schema / properties / categories / items / enum

Previous value: -[
-  "passthrough",
-  "hris",
-  "ats",
-  "auth",
-  "crm",
-  "enrich",
-  "martech",
-  "ticketing",
-  "uc",
-  "accounting",
-  "storage",
-  "commerce",
-  "payment",
-  "genai",
-  "messaging",
-  "kms",
-  "task",
-  "scim",
-  "lms",
-  "repo",
-  "metadata",
-  "calendar",
-  "verification"
-]New value: +[
+  "passthrough",
+  "hris",
+  "ats",
+  "auth",
+  "crm",
+  "enrich",
+  "martech",
+  "ticketing",
+  "uc",
+  "accounting",
+  "storage",
+  "commerce",
+  "payment",
+  "genai",
+  "messaging",
+  "kms",
+  "task",
+  "scim",
+  "lms",
+  "repo",
+  "metadata",
+  "calendar",
+  "verification",
+  "ads",
+  "forms",
+  "shipping",
+  "assessment"
+]

removedInput schema / properties / fields

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

addedInput schema / properties / updated_gte / description

Added value: +"(ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)"

First observedFeb 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that it 'Returns an array of integration records' and lists supported filters, which goes beyond the annotations. No contradictions.

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?

Two sentences with zero waste. The purpose is front-loaded, and the filter list and usage guidance are concise and directly relevant.

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?

For a list tool with 8 parameters and no output schema, the description provides the essential return type, filter list, and usage context. It does not detail return record structure or pagination mechanics, but the schema covers limit/offset. Overall, it is adequate for correct invocation.

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 75%, with 'env' and 'summary' having no schema descriptions. The description lists these filters but does not elaborate on their meaning. For parameters with schema descriptions, it adds little beyond repetition. Thus, it partially compensates but does not fully fill the gaps.

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?

The description states the specific verb and resource: 'List integrations from the connected account.' It also mentions the return type and filter capabilities. The name itself clearly distinguishes it from sibling tools that list other resources (connections, environments, webhooks).

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?

The description explicitly says 'Use to browse or search many integrations,' which gives clear context for when to invoke it. It does not explicitly exclude alternatives or mention single-resource retrieval, but the scope is clear enough given the sibling list tools.

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

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?