DexPaprika (CoinPaprika)

Official

Overview Schema Source Related Servers Discussions Admin

getPoolTransactions

Read-onlyIdempotent

Get a DEX pool's recent individual swap transactions, newest first, with time filters and pagination. Use to show recent trades or check who swapped recently.

Instructions

Get one pool's recent individual swap transactions, newest first, returned under 'transactions' (paginate with page, or a cursor). Read-only and keyless. These are per-trade records, not aggregated candles (use getPoolOHLCV) or a summary snapshot (use getPoolDetails). Use for 'recent trades on this pool', 'who swapped in the last hour', or 'raw transaction feed'. Params: network (required); pool_address (required); limit (default 10, max 100); page (default 1, up to 100 pages) or cursor (a transaction id); from (optional Unix seconds, inclusive, capped to the last 7 days); to (optional Unix seconds, exclusive, must be after from).

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	OPTIONAL: Filter transactions up to this UNIX timestamp (exclusive). Must be after 'from'.
`from`	No	OPTIONAL: Filter transactions starting from this UNIX timestamp (inclusive). Results always capped to last 7 days.
`page`	No	OPTIONAL: Page number for pagination, up to 100 pages (default: 1, 1-indexed)
`limit`	No	OPTIONAL: Number of items per page (default: 10, max: 100)
`cursor`	No	OPTIONAL: Transaction ID used for cursor-based pagination
`network`	Yes	REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
`rationale`	Yes	REQUIRED. 1-2 sentence rationale for this call (e.g. "User asked for X; calling Y to fetch Z"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions` field for the full convention and worked examples.
`pool_address`	Yes	REQUIRED: Pool address or identifier

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page_info`	Yes
`transactions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv1.0.1Jun 24, 2026

changedInput schema / properties / cursor / description

Previous value: -"Transaction ID used for cursor-based pagination"New value: +"OPTIONAL: Transaction ID used for cursor-based pagination"

addedInput schema / properties / from

Added value: +{
+  "description": "OPTIONAL: Filter transactions starting from this UNIX timestamp (inclusive). Results always capped to last 7 days.",
+  "type": "number"
+}

changedInput schema / properties / limit / description

Previous value: -"Number of items per page (max 100)"New value: +"OPTIONAL: Number of items per page (default: 10, max: 100)"

changedInput schema / properties / network / description

Previous value: -"Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"New value: +"REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')"

changedInput schema / properties / page / default
```
Previous value: -0New value: +1
```

changedInput schema / properties / page / description

Previous value: -"Page number for pagination (up to 100 pages)"New value: +"OPTIONAL: Page number for pagination, up to 100 pages (default: 1, 1-indexed)"

removedInput schema / properties / poolAddress

Removed value: -{
-  "description": "Pool address or identifier",
-  "type": "string"
-}

addedInput schema / properties / pool_address

Added value: +{
+  "description": "REQUIRED: Pool address or identifier",
+  "type": "string"
+}

addedInput schema / properties / rationale

Added value: +{
+  "description": "REQUIRED. 1-2 sentence rationale for this call (e.g. \"User asked for X; calling Y to fetch Z\"). Logged for MCP improvement, never shown to end users. No PII or secrets. See the server `instructions` field for the full convention and worked examples.",
+  "maxLength": 500,
+  "minLength": 20,
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "OPTIONAL: Filter transactions up to this UNIX timestamp (exclusive). Must be after 'from'.",
+  "type": "number"
+}

changedInput schema / required

Previous value: -[
-  "network",
-  "poolAddress"
-]New value: +[
+  "network",
+  "pool_address",
+  "rationale"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "page_info": {
+      "additionalProperties": true,
+      "properties": {
+        "limit": {
+          "description": "Items per page in the request.",
+          "type": "number"
+        },
+        "page": {
+          "description": "Current page number (1-indexed).",
+          "type": "number"
+        },
+        "total_items": {
+          "description": "Total number of items across all pages.",
+          "type": "number"
+        },
+        "total_pages": {
+          "description": "Total number of pages available.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "transactions": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "amount_usd": {
+            "type": "number"
+          },
+          "block_number": {
+            "type": "number"
+          },
+          "block_timestamp": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "pool_id": {
+            "type": "string"
+          },
+          "token0": {},
+          "token1": {}
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "transactions",
+    "page_info"
+  ],
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds key behaviors: 'keyless', pagination via page/cursor, time filter with 7-day cap, and result structure ('under transactions'). 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?

Concise yet comprehensive: core action first, then differentiation, use cases, parameter details. Every sentence adds value; no redundancy.

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

Completeness5/5

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

Given output schema exists (not shown), return values need no further explanation. All parameters are fully covered, behavior and constraints clear. Completes the picture for effective tool invocation.

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 100%, but the description enriches understanding with defaults, limits, pagination types, and time constraints. It explains response format and parameter relationships beyond the schema.

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 the tool retrieves a pool's recent swap transactions, newest first, and distinguishes itself from related tools like getPoolOHLCV and getPoolDetails.

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 provides use cases ('recent trades on this pool', 'who swapped in the last hour', 'raw transaction feed') and contrasts with other tools ('not aggregated candles' or summary snapshots).

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

Deploy Server