DexPaprika

filterNetworkTokens

Read-onlyIdempotent

Get tokens on one network matching numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only and keyless. Choose this over getTopTokens when the user gives numeric constraints or a time window. Use for 'tokens with FDV over $10M on Base', 'newly created tokens today', or 'low-liquidity high-volume tokens'. Optional filters (AND-combined): volume_24h_min/max, liquidity_usd_min/max, fdv_min/max, txns_24h_min, price_change_percentage_24h_min/max, created_after/created_before (a relative offset such as '-24h', Unix seconds, RFC3339 or YYYY-MM-DD). Also network (required); limit (default 50, max 100); cursor to page; sort_by (default 'volume_usd_24h', alias order_by); sort_dir asc/desc (default 'desc', alias sort). Pools and tokens created in the last hour are left out: this server searches like a free key, so a created_after window shorter than an hour comes back empty. A Dev plan or higher on your own key, calling the API directly, sees them as they are indexed.

Input Schema

Name	Required	Description
`sort`	No	OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly.
`limit`	No	OPTIONAL: Items per page (default: 50, max: 100)
`cursor`	No	OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.
`fdv_max`	No	OPTIONAL: Maximum FDV in USD
`fdv_min`	No	OPTIONAL: Minimum FDV in USD
`network`	Yes	REQUIRED: Network ID from getNetworks
`sort_by`	No	OPTIONAL: Sort field. Defaults to 'volume_usd_24h'. Prefer the canonical names; short legacy names are still accepted. The REST API calls this parameter order_by.
`order_by`	No	OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly.
`sort_dir`	No	OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort.
`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.
`txns_24h_min`	No	OPTIONAL: Minimum transactions in 24h
`created_after`	No	OPTIONAL: Only tokens created at or after this time: a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or YYYY-MM-DD
`created_before`	No	OPTIONAL: Only tokens created at or before this time, same formats as created_after (e.g. '-1h')
`volume_24h_max`	No	OPTIONAL: Maximum 24h volume in USD
`volume_24h_min`	No	OPTIONAL: Minimum 24h volume in USD
`liquidity_usd_max`	No	OPTIONAL: Maximum token liquidity in USD
`liquidity_usd_min`	No	OPTIONAL: Minimum token liquidity in USD
`price_change_percentage_24h_max`	No	OPTIONAL: Maximum 24h price change, in percent
`price_change_percentage_24h_min`	No	OPTIONAL: Minimum 24h price change, in percent. Negatives are allowed, so -20 finds tokens down at least 20%. This is the only price-change window tokens carry; for 6h, 1h or 5m use getNetworkPoolsFilter.

Output Schema

Name	Required	Description
`query`	No	Echo of the resolved query and filters the API applied.
`results`	Yes
`next_cursor`	No	Opaque pagination cursor. Pass back as the `cursor` argument to fetch the next page; null/absent on the last page.
`has_next_page`	No	True if more results are available; fetch them by passing next_cursor as `cursor`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 23, 2026

changedOutput schema / properties / has_next_page / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

removedOutput schema / properties / query / additionalProperties
```
Removed value: -{}
```

addedOutput schema / properties / query / anyOf

Added value: +[
+  {
+    "additionalProperties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / query / type
```
Removed value: -"object"
```
removedOutput schema / properties / results / items / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties / results / items / anyOf

Added value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "added_at": {
+        "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "chain": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "decimals": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "fdv": {
+        "description": "Fully-diluted valuation in USD.",
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Token contract address (chain-canonical form).",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "symbol": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / results / items / properties

Removed value: -{
-  "added_at": {
-    "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
-    "type": "string"
-  },
-  "chain": {
-    "type": "string"
-  },
-  "decimals": {
-    "type": "number"
-  },
-  "fdv": {
-    "description": "Fully-diluted valuation in USD.",
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  "id": {
-    "description": "Token contract address (chain-canonical form).",
-    "type": "string"
-  },
-  "name": {
-    "type": "string"
-  },
-  "symbol": {
-    "type": "string"
-  }
-}

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

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / created_after / description

Previous value: -"OPTIONAL: Only tokens created after this UNIX timestamp"New value: +"OPTIONAL: Only tokens created at or after this time: a relative offset such as '-24h' or '-7d', Unix seconds, RFC3339 or YYYY-MM-DD"

changedInput schema / properties / created_after / type
```
Previous value: -"number"New value: +"string"
```

changedInput schema / properties / created_before / description

Previous value: -"OPTIONAL: Only tokens created before this UNIX timestamp"New value: +"OPTIONAL: Only tokens created at or before this time, same formats as created_after (e.g. '-1h')"

changedInput schema / properties / created_before / type
```
Previous value: -"number"New value: +"string"
```

Changed3 schema fields changedSep 2, 2026

addedInput schema / properties / price_change_percentage_24h_max

Added value: +{
+  "description": "OPTIONAL: Maximum 24h price change, in percent",
+  "type": "number"
+}

addedInput schema / properties / price_change_percentage_24h_min

Added value: +{
+  "description": "OPTIONAL: Minimum 24h price change, in percent. Negatives are allowed, so -20 finds tokens down at least 20%. This is the only price-change window tokens carry; for 6h, 1h or 5m use getNetworkPoolsFilter.",
+  "type": "number"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "has_next_page": {
+      "description": "True if more results are available; fetch them by passing next_cursor as `cursor`.",
+      "type": "boolean"
+    },
+    "next_cursor": {
+      "description": "Opaque pagination cursor. Pass back as the `cursor` argument to fetch the next page; null/absent on the last page.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "query": {
+      "additionalProperties": {},
+      "description": "Echo of the resolved query and filters the API applied.",
+      "type": "object"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "added_at": {
+            "description": "ISO 8601 timestamp when DexPaprika first indexed this token.",
+            "type": "string"
+          },
+          "chain": {
+            "type": "string"
+          },
+          "decimals": {
+            "type": "number"
+          },
+          "fdv": {
+            "description": "Fully-diluted valuation in USD.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Token contract address (chain-canonical form).",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "symbol": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 13, 2026

removedInput schema / properties / price_change_percentage_24h_max

Removed value: -{
-  "description": "OPTIONAL: Maximum 24h price change, in percent",
-  "type": "number"
-}

removedInput schema / properties / price_change_percentage_24h_min

Removed value: -{
-  "description": "OPTIONAL: Minimum 24h price change, in percent. Negatives are allowed, so -20 finds tokens down at least 20%. This is the only price-change window tokens carry; for 6h, 1h or 5m use getNetworkPoolsFilter.",
-  "type": "number"
-}

Changed2 schema fields changedAug 7, 2026

addedInput schema / properties / price_change_percentage_24h_max

Added value: +{
+  "description": "OPTIONAL: Maximum 24h price change, in percent",
+  "type": "number"
+}

addedInput schema / properties / price_change_percentage_24h_min

Added value: +{
+  "description": "OPTIONAL: Minimum 24h price change, in percent. Negatives are allowed, so -20 finds tokens down at least 20%. This is the only price-change window tokens carry; for 6h, 1h or 5m use getNetworkPoolsFilter.",
+  "type": "number"
+}

Changed4 schema fields changedJul 30, 2026

changedInput schema / properties / order_by / description

Previous value: -"DEPRECATED alias for sort_by. Both accepted; prefer sort_by going forward."New value: +"OPTIONAL: alias of sort_by; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes order_by, so use this name when calling the REST API directly."

changedInput schema / properties / sort / description

Previous value: -"DEPRECATED alias for sort_dir. Both accepted; prefer sort_dir going forward."New value: +"OPTIONAL: alias of sort_dir; both are accepted. Not deprecated at the REST layer: api.dexpaprika.com itself takes sort, so use this name when calling the REST API directly."

changedInput schema / properties / sort_by / description

Previous value: -"OPTIONAL: Sort field. Defaults to 'volume_usd_24h'. Prefer the canonical names; short legacy names are still accepted."New value: +"OPTIONAL: Sort field. Defaults to 'volume_usd_24h'. Prefer the canonical names; short legacy names are still accepted. The REST API calls this parameter order_by."

changedInput schema / properties / sort_dir / description

Previous value: -"OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided."New value: +"OPTIONAL: Sort direction (asc/desc). Canonical parameter name. Defaults to 'desc' if neither sort_dir nor sort is provided. The REST API calls this parameter sort."

First observedJul 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations it discloses the return envelope (results/has_next_page/next_cursor), that filters are AND-combined, and a non-obvious data gap: tokens and pools created in the last hour are omitted on the free/keyless tier, so sub-hour created_after windows return empty. That is genuinely useful behavioral context that annotations cannot express, though the 'read-only and keyless' clause largely restates readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Usage guidance and the response envelope are front-loaded, which is good, but the middle enumerates every filter and its default in a form that repeats the schema verbatim, and the closing sentence about the Dev plan/own API key is tangential to calling this tool. Roughly a third of the text could be cut without losing decision-relevant information.

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?

For a 19-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent still needs: when to pick it over siblings, filter-combination semantics, pagination via cursor, and the recently-created-token blind spot. Return values are correctly left to the output schema.

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 already 100%, so baseline is 3; the description still adds real meaning by declaring the filter set AND-combined, spelling out accepted time formats for created_after/created_before, and noting the sort_by/order_by and sort_dir/sort aliases with their defaults. It does duplicate several schema-documented defaults (limit 50/max 100) rather than adding to them.

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 tokens on one network matching numeric thresholds') plus the response envelope, and explicitly contrasts with the sibling getTopTokens. An agent can distinguish it from getTopTokens, getNetworkPoolsFilter, and getTokenDetails without opening a 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?

Gives an explicit selection rule ('Choose this over getTopTokens when the user gives numeric constraints or a time window') and three concrete example queries that map user phrasing to this tool. It also names the fallback for other price-change windows (getNetworkPoolsFilter).

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?