Skip to main content
Glama

getNFTMetadata

Retrieve metadata for NFTs on Ethereum networks by providing contract address and token ID to access detailed token information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contractAddressYes
tokenIdYes
providerNo
chainIdNo

Implementation Reference

  • Registration of the getNFTMetadata MCP tool, including inline Zod input schema and async handler function that delegates to getMetadata service.
        "getNFTMetadata",
        {
          contractAddress: contractAddressSchema,
          tokenId: tokenIdSchema,
          provider: providerSchema,
          chainId: chainIdSchema
        },
        async ({ contractAddress, tokenId, provider, chainId }) => {
          try {
            const metadata = await getMetadata(ethersService, contractAddress, tokenId.toString(), provider, chainId);
            return {
              content: [{ 
                type: "text", 
                text: `NFT #${tokenId} Metadata:
    Name: ${metadata.name || 'No name available'}
    Description: ${metadata.description || 'No description available'}
    Image URL: ${metadata.image || 'No image available'}`
              }]
            };
          } catch (error) {
            return {
              isError: true,
              content: [{ 
                type: "text", 
                text: `Error getting token metadata: ${error instanceof Error ? error.message : String(error)}`
              }]
            };
          }
        }
      );
  • TypeScript type definition for GetNFTMetadataParams matching the tool input schema.
    type GetNFTMetadataParams = {
      contractAddress: string;
      tokenId: string | number;
      provider?: string;
      chainId?: number;
    };
  • Helper function getMetadata that implements the core logic: caches token URI, fetches and parses metadata from URI, handles errors and caching.
    export async function getMetadata(
      ethersService: EthersService,
      contractAddress: string,
      tokenId: string | number,
      provider?: string,
      chainId?: number
    ): Promise<NFTMetadata> {
      metrics.incrementCounter('erc721.getMetadata');
      
      return timeAsync('erc721.getMetadata', async () => {
        try {
          // Create cache key
          const cacheKey = createTokenCacheKey(
            CACHE_KEYS.ERC721_METADATA,
            contractAddress,
            tokenId,
            chainId
          );
          
          // Check cache first
          const cachedMetadata = contractCache.get(cacheKey);
          if (cachedMetadata) {
            return cachedMetadata as NFTMetadata;
          }
          
          // Get token URI
          const tokenURI = await getTokenURI(ethersService, contractAddress, tokenId, provider, chainId);
          
          // Fetch and parse metadata
          const metadata = await fetchMetadata(tokenURI, contractAddress, tokenId);
          
          // Cache result for future use (1 hour TTL)
          contractCache.set(cacheKey, metadata, { ttl: 3600000 });
          
          return metadata;
        } catch (error) {
          logger.debug('Error getting NFT metadata', { contractAddress, tokenId, error });
          
          if (error instanceof TokenNotFoundError) {
            throw error;
          }
          
          // Handle metadata parsing errors
          if (!(error instanceof TokenMetadataError)) {
            throw new TokenMetadataError(contractAddress, tokenId, undefined, {
              originalError: error instanceof Error ? error.message : String(error)
            });
          }
          
          throw error;
        }
      });
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/crazyrabbitLTC/mcp-ethers-server'

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