Coinmarketcap

Listings Latest

listings_latest

Read-onlyIdempotent

Paginated list of cryptocurrencies ranked by market cap (or volume/price-change); returns rank, price, market cap, 24h volume, and 24h change per coin. Sortable; up to 5000 results.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	market_cap \| volume_24h \| percent_change_24h \| name \| symbol
`limit`	No	1-5000 (default 20)
`start`	No	1-based rank offset (default 1)
`convert`	No	Quote currency (default USD)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Array of top-ranked cryptocurrencies
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10
+  },
+  {
+    "convert": "USD",
+    "limit": 50,
+    "sort": "market_cap",
+    "start": 1
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Array of top-ranked cryptocurrencies",
+      "items": {
+        "properties": {
+          "circulating_supply": {
+            "description": "Circulating supply",
+            "type": "number"
+          },
+          "cmc_rank": {
+            "description": "Market cap rank",
+            "type": "integer"
+          },
+          "date_added": {
+            "description": "Date added to CMC",
+            "type": "string"
+          },
+          "id": {
+            "description": "CMC cryptocurrency ID",
+            "type": "integer"
+          },
+          "last_updated": {
+            "description": "Last update ISO timestamp",
+            "type": "string"
+          },
+          "max_supply": {
+            "description": "Maximum supply cap",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Cryptocurrency name",
+            "type": "string"
+          },
+          "num_market_pairs": {
+            "description": "Number of trading pairs",
+            "type": "integer"
+          },
+          "platform": {
+            "description": "Blockchain platform info",
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "quote": {
+            "description": "Price quotes in requested currency",
+            "type": "object"
+          },
+          "slug": {
+            "description": "URL-friendly slug",
+            "type": "string"
+          },
+          "symbol": {
+            "description": "Ticker symbol",
+            "type": "string"
+          },
+          "tags": {
+            "description": "Associated tags",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "total_supply": {
+            "description": "Total supply",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "properties": {
+        "credit_count": {
+          "description": "API credits consumed",
+          "type": "integer"
+        },
+        "elapsed": {
+          "description": "Elapsed milliseconds",
+          "type": "integer"
+        },
+        "error_code": {
+          "description": "Error code (0 for success)",
+          "type": "integer"
+        },
+        "error_message": {
+          "description": "Error message if applicable",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "timestamp": {
+          "description": "ISO timestamp of the quote",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. Description adds sortability, pagination limit, and returned fields, providing full behavioral transparency beyond 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?

Single sentence front-loaded with key information; every part adds value. No fluff.

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 output schema present, description covers purpose, parameters, and results adequately. Annotations provide safety profile. Complete for a list tool.

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% with detailed parameter descriptions. The description reiterates some info (sortability, limit) but does not add substantial new meaning 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?

Explicitly states it returns a paginated list of cryptocurrencies ranked by market cap or other metrics, with specific fields. Distinguishes from sibling tools like 'categories' or 'global_metrics'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context for use (ranking, sorting, pagination) but no explicit when-not-to-use or direct sibling comparison.

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

All Coinmarketcap 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.