Skip to main content
Glama
IAcomunIA

CoinGecko MCP Server

by IAcomunIA

get_markets_nfts

Read-only

Query NFT collections on CoinGecko to retrieve market data including floor prices, market capitalization, trading volume, and related metrics for analysis and tracking.

Instructions

When using this tool, always use the jq_filter parameter to reduce the response size and improve performance.

Only omit if you're sure you don't need the data.

This endpoint allows you to query all the supported NFT collections with floor price, market cap, volume and market related data on CoinGecko

Response Schema

{
  $ref: '#/$defs/nft_get_markets_response',
  $defs: {
    nft_get_markets_response: {
      type: 'array',
      items: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'NFT collection ID'
          },
          asset_platform_id: {
            type: 'string',
            description: 'NFT collection asset platform ID'
          },
          contract_address: {
            type: 'string',
            description: 'NFT collection contract address'
          },
          description: {
            type: 'string',
            description: 'NFT collection description'
          },
          floor_price: {
            type: 'object',
            description: 'NFT collection floor price',
            properties: {
              native_currency: {
                type: 'number'
              },
              usd: {
                type: 'number'
              }
            }
          },
          floor_price_24h_percentage_change: {
            type: 'object',
            description: 'NFT collection floor price 24 hours percentage change',
            properties: {
              native_currency: {
                type: 'number'
              },
              usd: {
                type: 'number'
              }
            }
          },
          floor_price_in_usd_24h_percentage_change: {
            type: 'number',
            description: 'NFT collection floor price in usd 24 hours percentage change'
          },
          image: {
            type: 'object',
            description: 'NFT collection image url',
            properties: {
              small: {
                type: 'string'
              },
              small_2x: {
                type: 'string'
              }
            }
          },
          market_cap: {
            type: 'object',
            description: 'NFT collection market cap',
            properties: {
              native_currency: {
                type: 'number'
              },
              usd: {
                type: 'number'
              }
            }
          },
          market_cap_24h_percentage_change: {
            type: 'object',
            description: 'NFT collection market cap 24 hours percentage change',
            properties: {
              native_currency: {
                type: 'number'
              },
              usd: {
                type: 'number'
              }
            }
          },
          market_cap_rank: {
            type: 'number',
            description: 'coin market cap rank'
          },
          name: {
            type: 'string',
            description: 'NFT collection name'
          },
          native_currency: {
            type: 'string',
            description: 'NFT collection native currency'
          },
          native_currency_symbol: {
            type: 'string',
            description: 'NFT collection native currency symbol'
          },
          number_of_unique_addresses: {
            type: 'number',
            description: 'number of unique address owning the NFTs'
          },
          number_of_unique_addresses_24h_percentage_change: {
            type: 'number',
            description: 'number of unique address owning the NFTs 24 hours percentage change'
          },
          one_day_average_sale_price: {
            type: 'number',
            description: 'NFT collection one day average sale price'
          },
          one_day_average_sale_price_24h_percentage_change: {
            type: 'number',
            description: 'NFT collection one day average sale price 24 hours percentage change'
          },
          one_day_sales: {
            type: 'number',
            description: 'NFT collection one day sales'
          },
          one_day_sales_24h_percentage_change: {
            type: 'number',
            description: 'NFT collection one day sales 24 hours percentage change'
          },
          symbol: {
            type: 'string',
            description: 'NFT collection symbol'
          },
          total_supply: {
            type: 'number',
            description: 'NFT collection total supply'
          },
          volume_24h: {
            type: 'object',
            description: 'NFT collection volume in 24 hours',
            properties: {
              native_currency: {
                type: 'number'
              },
              usd: {
                type: 'number'
              }
            }
          },
          volume_24h_percentage_change: {
            type: 'object',
            description: 'NFT collection volume in 24 hours percentage change',
            properties: {
              native_currency: {
                type: 'number'
              },
              usd: {
                type: 'number'
              }
            }
          },
          volume_in_usd_24h_percentage_change: {
            type: 'number',
            description: 'NFT collection volume in usd 24 hours percentage change'
          }
        }
      }
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_platform_idNofilter result by asset platform (blockchain network) *refers to [`/asset_platforms`](/reference/asset-platforms-list) filter=`nft`
orderNosort results by field Default: `market_cap_usd_desc`
pageNopage through results Default: `1`
per_pageNototal results per page Valid values: any integer between 1 and 250 Default: `100`
jq_filterNoA jq filter to apply to the response to include certain fields. Consult the output schema in the tool description to see the fields that are available. For example: to include only the `name` field in every object of a results array, you can provide ".results[].name". For more information, see the [jq documentation](https://jqlang.org/manual/).
Behavior4/5

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

Annotations provide readOnlyHint=true, which the description doesn't contradict. The description adds valuable behavioral context beyond annotations: it emphasizes performance optimization through jq_filter usage, warns about potentially large response sizes, and describes the data scope (floor price, market cap, volume, market data). It doesn't mention rate limits, authentication needs, or pagination behavior, but with annotations covering safety, this adds meaningful context.

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

Conciseness2/5

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

The description is poorly structured: it starts with a usage tip about jq_filter, then states the purpose, and includes a full output schema that belongs in a separate field. The output schema duplication makes it verbose and unfocused, with sentences that don't efficiently earn their place in the core description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters, rich data), annotations cover read-only safety, but there's no output schema in structured fields (the description embeds one). The description provides purpose and some behavioral context, but lacks details on pagination defaults, error handling, or data freshness. It's adequate but has gaps for a data query tool with multiple parameters.

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 description coverage is 100%, so the schema fully documents all 5 parameters. The description mentions jq_filter specifically for performance, adding some practical guidance beyond the schema's technical documentation. However, it doesn't explain the semantics of other parameters like 'order' or 'asset_platform_id' beyond what the schema provides, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'query all the supported NFT collections with floor price, market cap, volume and market related data on CoinGecko'. It specifies the verb ('query'), resource ('NFT collections'), and scope ('all supported'), but doesn't explicitly differentiate from sibling tools like 'get_list_nfts' or 'get_nfts_market_chart', which appear related.

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

Usage Guidelines3/5

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

The description provides some usage guidance by recommending 'always use the `jq_filter` parameter to reduce response size and improve performance', with a conditional 'Only omit if you're sure you don't need the data'. However, it doesn't specify when to use this tool versus alternatives like 'get_list_nfts' or 'get_nfts_market_chart' from the sibling list, leaving the context implied rather than explicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IAcomunIA/MCP_firts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server