DexPaprika (CoinPaprika)

Official

Overview Schema Source Related Servers Discussions Admin

filterNetworkTokens

Read-onlyIdempotent

Filter tokens on one network by 24h volume, liquidity, FDV, transactions, price change, or creation time to find assets matching numeric thresholds or time windows.

Instructions

Get tokens on one network matching numeric thresholds, returned under 'results' with has_next_page and next_cursor. Read-only. The first page works without an API key; paging with cursor needs a key (a free key pages without limit). 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).

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: Number of items per page (default: 50, max: 100)
`cursor`	No	OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page; needs an API key (a free key pages without limit). Replaces the old page number.
`fdv_max`	No	OPTIONAL: Maximum fully diluted valuation in USD
`fdv_min`	No	OPTIONAL: Minimum fully diluted valuation in USD
`network`	Yes	REQUIRED: Network ID from getNetworks (e.g., 'ethereum', 'solana')
`sort_by`	No	OPTIONAL (preferred): Field to sort by (default: '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 (preferred): Sort direction (default: 'desc'). 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 number of 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	Default
`query`	No
`results`	No
`next_cursor`	No
`has_next_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.9.0Oct 16, 2026

changedInput schema / properties / cursor / description

Previous value: -"OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number."New value: +"OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page; needs an API key (a free key pages without limit). Replaces the old page number."

Changed4 schema fields changedv2.7.1Oct 1, 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"
```

Changed2 schema fields changedv2.5.0Aug 19, 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 changedv2.3.2Jul 30, 2026

changedInput schema / properties / order_by / description

Previous value: -"OPTIONAL (deprecated alias of sort_by): Field to sort by"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: -"OPTIONAL (deprecated alias of sort_dir): Sort direction"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 (preferred): Field to sort by (default: 'volume_usd_24h'). Prefer the canonical names; short legacy names are still accepted."New value: +"OPTIONAL (preferred): Field to sort by (default: '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 (preferred): Sort direction (default: 'desc')"New value: +"OPTIONAL (preferred): Sort direction (default: 'desc'). The REST API calls this parameter sort."

Changed10 schema fields changedv1.0.2Jul 29, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "OPTIONAL: Pagination cursor. Pass `next_cursor` from a previous response to fetch the next page. Replaces the old page number.",
+  "type": "string"
+}

addedInput schema / properties / liquidity_usd_max

Added value: +{
+  "description": "OPTIONAL: Maximum token liquidity in USD",
+  "type": "number"
+}

changedInput schema / properties / order_by / enum

Previous value: -[
-  "volume_24h",
-  "volume_7d",
-  "volume_30d",
-  "liquidity_usd",
-  "txns_24h",
-  "created_at",
-  "fdv"
-]New value: +[
+  "volume_usd_24h",
+  "volume_usd_7d",
+  "volume_usd_30d",
+  "liquidity_usd",
+  "txns_24h",
+  "fdv_usd",
+  "created_at",
+  "price_change_percentage_24h",
+  "volume_24h",
+  "volume_7d",
+  "volume_30d",
+  "txns",
+  "price_change",
+  "fdv",
+  "price_usd"
+]

removedInput schema / properties / page

Removed value: -{
-  "default": 1,
-  "description": "OPTIONAL: Page number for pagination (default: 1, 1-indexed)",
-  "type": "number"
-}

changedInput schema / properties / sort_by / description

Previous value: -"OPTIONAL (preferred): Field to sort by (default: 'volume_24h')"New value: +"OPTIONAL (preferred): Field to sort by (default: 'volume_usd_24h'). Prefer the canonical names; short legacy names are still accepted."

changedInput schema / properties / sort_by / enum

Previous value: -[
-  "volume_24h",
-  "volume_7d",
-  "volume_30d",
-  "liquidity_usd",
-  "txns_24h",
-  "created_at",
-  "fdv"
-]New value: +[
+  "volume_usd_24h",
+  "volume_usd_7d",
+  "volume_usd_30d",
+  "liquidity_usd",
+  "txns_24h",
+  "fdv_usd",
+  "created_at",
+  "price_change_percentage_24h",
+  "volume_24h",
+  "volume_7d",
+  "volume_30d",
+  "txns",
+  "price_change",
+  "fdv",
+  "price_usd"
+]

addedOutput schema / properties / has_next_page
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / next_cursor

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

removedOutput schema / properties / page_info

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

addedOutput schema / properties / query

Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}

Addedv1.0.1Jun 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the restatement of 'Read-only' earns little. What the description adds beyond the annotations is genuinely useful: first-page access without an API key versus cursor paging requiring a key, plus the documented return envelope ('results' with has_next_page and next_cursor). It stops short of describing rate limits or error behavior.

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?

The purpose, the output envelope and the auth constraint are front-loaded, and the sibling comparison comes before the filter inventory. It is a dense single block, and re-listing every optional filter with its min/max pair largely repeats schema content that is already fully documented, so it is slightly longer than it needs to be.

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 filtered-list tool, the description covers the usage trigger, the required network argument, pagination and its auth implication, sorting, and the report of the return envelope. With an output schema present, no further explanation of return values is required, so nothing an agent needs to call this correctly is missing.

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, and much of the inline filter enumeration duplicates the schema. The description does add meaning the schema lacks at a whole-object level: that the optional filters are AND-combined, the defaults/max for limit and sort, and the alias pairs (order_by/sort_by, sort/sort_dir). That grouping context is what lifts it above baseline.

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') plus the qualifying scope ('matching numeric thresholds'). It explicitly contrasts itself with getTopTokens, so an agent can route between the two without opening either 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 backs it with concrete trigger examples ('tokens with FDV over $10M on Base', 'newly created tokens today'). When-to-use and the alternative are both stated, not implied.

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