Unified.to MCP Server

List API calls

list_unified_apicalls

Read-onlyIdempotent

List apicalls from the connected account. Returns an array of apicall records. Supports filtering by updated_gte, sort, order, external_xref, integration_type, error, connection_id, env, and pagination. Use to browse or search many apicalls; to fetch a single apicall by its ID, use get_unified_apicall.

Input Schema

Name	Required	Description
`env`	No
`sort`	No
`type`	No	Filter the results to just this type
`error`	No	Filter the results for API Calls with errors
`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.
`webhook_id`	No	Filter the results to just this webhook
`is_billable`	No	Filter the results for only billable API Calls
`updated_gte`	No	Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
`connection_id`	No	Filter the results to just this integration
`external_xref`	No	Filter the results to only those integrations for your user referenced by this value
`integration_type`	No	Filter the results to just this integration

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": {
+    "ApiCall": {
+      "properties": {
+        "connection_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "created_at": {
+          "description": "The date that this object was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "endapi_response_time": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "environment": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "error": {
+          "description": "The error description (if status code is >= 400)",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "external_xref": {
+          "description": "your customer's user ID",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Unique identifier for this API call",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "integration_type": {
+          "description": "The integration type",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ip_address": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "is_billable": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "method": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "The called name of the API method",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "path": {
+          "description": "The called API method's HTTP verb and route path (PUT /crm/{integration}/deak/{id})",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "size": {
+          "description": "The size of the response",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "The resulting HTTP status code (200)",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "type": {
+          "description": "The type of API Call being logged. One of: login, webhook, inbound, mcp",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "unified_response_time": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "user_agent": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "webhook_id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "workspace_id": {
+          "description": "(reference to KmsSpace)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    }
+  },
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "results": {
+      "items": {
+        "anyOf": [
+          {
+            "$ref": "#/$defs/ApiCall"
+          },
+          {
+            "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)"

Changed3 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 / type / enum

Previous value: -[
-  "login",
-  "webhook",
-  "inbound"
-]New value: +[
+  "login",
+  "webhook",
+  "inbound",
+  "mcp"
+]

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.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description's additional disclosure is thin: it notes the return type (already covered by the output schema) and lists filter fields, but doesn't add behavioral context like pagination limits, ordering defaults, or result-set caveats beyond the schema.

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, then return shape, then filter list, then routing guidance. Efficient and well-ordered, though the inline filter enumeration is somewhat list-heavy and partly redundant with the schema.

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 covering return values and annotations covering the safety profile, the description provides enough to call correctly: purpose, filtering capabilities, pagination awareness, and sibling routing. Minor gap in not clarifying defaults or enum meanings, but nothing critical is missing.

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 77%, near the high band, so the schema does most of the work for the 13 parameters. The description enumerates several filter fields but adds no syntax or format detail beyond what the schema documents, and it collapses limit/offset into the vague word 'pagination'. Baseline 3 is appropriate.

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 (apicalls) with scope ('from the connected account') and return shape ('array of apicall records'). It also explicitly distinguishes itself from get_unified_apicall, so an agent can route correctly without opening schemas.

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 states when to use it ('browse or search many apicalls') and names the alternative with the selecting condition ('to fetch a single apicall by its ID, use get_unified_apicall'). Nothing is left to inference.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?