DexPaprika

getPoolTransactions

Read-onlyIdempotent

Get one pool's recent individual swap transactions, newest first, returned under 'transactions' (paginate with page, or a cursor). Read-only. Runs on the caller's own Dev, Pro or Enterprise API key, set as the Authorization header on the connection to this server; without one it returns DP401_API_KEY_REQUIRED and sends nothing upstream, and a free key gets 403. In either case getPoolDetails still gives the pool's 24h transaction counts and volume. 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, inclusive: a relative offset such as '-1h', Unix seconds, RFC3339 or YYYY-MM-DD; capped to the last 7 days); to (optional, exclusive, same formats, must be after from).

Input Schema

Name	Required	Description
`to`	No	OPTIONAL: Filter transactions up to this time (exclusive), same formats as from. Must be after 'from'.
`from`	No	OPTIONAL: Filter transactions starting from this time (inclusive): a relative offset such as '-1h' or '-24h', Unix seconds, RFC3339 or YYYY-MM-DD. Results always capped to last 7 days.
`page`	No	OPTIONAL: Page number, 1-indexed. Up to 100 pages. Server accepts page=0 (treated as page=1) for backward compatibility.
`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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 23, 2026

removedOutput schema / properties / page_info / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / page_info / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "limit": {
+        "description": "Items per page in the request.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "page": {
+        "description": "Current page number (1-indexed).",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "total_items": {
+        "description": "Total number of items across all pages.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "total_pages": {
+        "description": "Total number of pages available.",
+        "type": [
+          "number",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / page_info / properties

Removed value: -{
-  "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"
-  }
-}

removedOutput schema / properties / page_info / type
```
Removed value: -"object"
```
removedOutput schema / properties / transactions / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / transactions / items / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "amount_usd": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "block_number": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "block_timestamp": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "pool_id": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "token0": {},
+      "token1": {}
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / transactions / items / properties

Removed value: -{
-  "amount_usd": {
-    "type": "number"
-  },
-  "block_number": {
-    "type": "number"
-  },
-  "block_timestamp": {
-    "type": "string"
-  },
-  "id": {
-    "type": "string"
-  },
-  "pool_id": {
-    "type": "string"
-  },
-  "token0": {},
-  "token1": {}
-}

removedOutput schema / properties / transactions / items / type
```
Removed value: -"object"
```

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / from / description

Previous value: -"OPTIONAL: Start of time-range filter, Unix epoch SECONDS (inclusive). Window is capped to last 7 days. Note: getPoolOHLCV uses `start` (string) for the same concept; getPoolTransactions uses numeric epoch for tighter filtering."New value: +"OPTIONAL: Filter transactions starting from this time (inclusive): a relative offset such as '-1h' or '-24h', Unix seconds, RFC3339 or YYYY-MM-DD. Results always capped to last 7 days."

changedInput schema / properties / from / type

Previous value: -"number"New value: +"string"

changedInput schema / properties / to / description

Previous value: -"OPTIONAL: Filter transactions up to this UNIX timestamp (exclusive). Must be after 'from'."New value: +"OPTIONAL: Filter transactions up to this time (exclusive), same formats as from. Must be after 'from'."

changedInput schema / properties / to / type

Previous value: -"number"New value: +"string"

Changed2 schema fields changedSep 2, 2026

changedInput schema / properties / from / description

Previous value: -"OPTIONAL: Start of time-range filter, Unix epoch SECONDS (inclusive). Window is capped to last 7 days. Note: getPoolOHLCV uses `start` (string) for the same concept — getPoolTransactions uses numeric epoch for tighter filtering."New value: +"OPTIONAL: Start of time-range filter, Unix epoch SECONDS (inclusive). Window is capped to last 7 days. Note: getPoolOHLCV uses `start` (string) for the same concept; getPoolTransactions uses numeric epoch for tighter filtering."

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 observedJul 28, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent, so the description is free to add what they cannot: API key tier requirements, the DP401_API_KEY_REQUIRED / 403 failure modes, no upstream request on missing key, the 7-day result cap, and newest-first ordering. That is substantial behavior beyond structured data.

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-loads the core action and output envelope, then auth, then sibling disambiguation, then params – a sensible order. It is dense and the middle auth sentence is long, but no sentence is filler.

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?

Output schema exists so return shape needn't be explained, and auth, caps, and alternatives are all covered. The one gap is the required 'rationale' parameter, which is never mentioned in the description and is a server-wide convention an agent might otherwise skip.

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 coverage is 100% and the 'Params:' list largely restates what the schema already documents (defaults, page cap, from/to formats, exclusivity of 'to'). It gives a convenient single-line summary but adds no new semantics, so the baseline 3 applies.

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 and resource ('get one pool's recent individual swap transactions, newest first') and explicitly distinguishes the output from getPoolOHLCV (aggregated candles) and getPoolDetails (summary snapshot). An agent can pick this tool without opening any 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?

Names the alternatives with the conditions that select them, plus concrete trigger phrases ('recent trades on this pool', 'who swapped in the last hour'). It also prescribes a fallback path when auth fails ('in either case getPoolDetails still gives...'), which is exactly the routing guidance an agent needs.

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

All DexPaprika 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?