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 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: 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.
`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

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds meaningful behavioral context: keyless access, newest-first ordering, response placement under 'transactions', pagination mechanics (page or cursor), and the 7-day window cap. No contradiction 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 information-dense but well organized: core behavior first, disambiguation second, use cases third, and a compact parameter summary. Every sentence earns its place without unnecessary padding.

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?

With 8 parameters, rich annotations, full schema coverage, and an output schema present, the description still adds essential usage context: pagination trade-offs, the capped date range, and sibling tool differentiation. Nothing critical is missing for correct 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%, so the baseline is 3. The description enhances semantics by grouping page and cursor as alternative pagination methods, explaining the response field 'transactions', and clarifying the from/to time-range semantics in compact form beyond individual schema descriptions.

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 a specific verb and resource: get one pool's recent individual swap transactions, newest first. It clearly distinguishes itself from getPoolOHLCV (aggregated candles) and getPoolDetails (summary snapshot), so an agent can select it correctly among siblings.

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 gives explicit when-to-use guidance with concrete examples ('recent trades on this pool', 'who swapped in the last hour', 'raw transaction feed') and names alternative tools to avoid. It also clarifies that this tool returns per-trade records, not 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.

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?