store_bundle_item_nft_metadata
Stores a single NFT bundle item's metadata to IPFS. Call once per NFT component in a bundle before store_bundle_metadata. Returns: { url: 'ipfs://...' } to include in the items array.
Category: Offer management.
Returns unsigned tx? Likely yes — sign locally and broadcast via send_signed_transaction or a meta-tx relay.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
schemaUrl | string | yes | |
type | ITEM_NFT | yes | |
name | string | yes | |
description | string | no | |
image | string | no | |
imageData | string | no | |
externalUrl | string | no | |
animationUrl | string | no | |
youtubeUrl | string | no | |
image_data | string | no | |
external_url | string | no | |
animation_url | string | no | |
youtube_url | string | no | |
attributes | object[] | no | |
chainId | number | no | |
contract | string | no | |
tokenId | string | no | |
tokenIdRange | object | no | |
terms | object[] | no | |
quantity | number | no | |
configId | string | yes | Boson/Fermion Protocol deployment identifier. Format: '<env>-<chainId>-<index>' e.g. 'production-137-0' (Polygon mainnet), 'testing-80002-0' (Amoy testnet). Call get_config_ids to list all valid values for this server. |
signerAddress | string | yes | Ethereum address that will sign and send this transaction. Must match the wallet that will sign the returned transaction locally. |
Related
- Reference → MCP tools — full catalogue.
- Build for AI agents → The 3-step signing pattern — what to do with returned unsigned transactions.
- Concepts → Signing & meta-transactions — canonical signing reference.