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

TableJSON 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)
`order`	No
`offset`	No	Number of results to skip, for pagination (default 0)
`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

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

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the return type ('Returns an array of apicall records') and the connected-account scope. No contradictions 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.

Conciseness5/5

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

The description is four short sentences, front-loaded with the core purpose, then return type, filter capabilities, and usage guidance. It contains no fluff and every sentence contributes to effective tool selection and invocation.

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 13-parameter list tool with no output schema, the description adequately communicates purpose, return array, pagination, and the sibling alternative. It omits a few filters (e.g., type, webhook_id, is_billable), but the schema covers these, so the description remains sufficient for correct use.

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%, slightly below the high threshold, so the schema still carries most parameter meaning. The description enumerates several filters and mentions pagination, but it adds little over the schema's own descriptions; it provides a helpful overview without deep semantic detail.

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 clearly states 'List apicalls from the connected account', specifying the verb, resource, and scope. It explicitly distinguishes itself from get_unified_apicall by directing single-ID lookups to that sibling, so an agent can immediately tell which tool to use.

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?

The description provides explicit when-to-use guidance: 'Use to browse or search many apicalls; to fetch a single apicall by its ID, use get_unified_apicall.' This names the alternative and the condition for choosing it, satisfying the when/when-not/alternatives requirement.

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?