← Back to all apps

Overview

Tools Available7
CategoryShopping

Style, decor, beauty, and more

Available Tools

Target provides 7 tools that can be used to interact with its services.

Check Availability

checkAvailability
Full Description

Checks item availability for a specific product (identified by TCIN). Returns shipping availability by default, and can also provide pickup and scheduled delivery options when location or store identifiers are supplied in the request. Use this tool to determine how and where an item can be fulfilled for a given customer location.

Parameters

Required
tcinstring

Target item number (TCIN)

Optional
scheduled_delivery_store_idstring

Store ID for scheduled delivery (optional)

store_idstring

Store ID for pickup (optional)

zipstring

ZIP code for availability check (optional)

Get Item Attributes

getItemAttributes
Full Description

Retrieve detailed metadata for a specific product identified by TCIN. Typically called after selecting an item after search or list Similar Items.

Parameters

Required
tcinstring

Target item number (TCIN)

Optional
pricing_store_idstring

Store ID for pricing information of the item at the specific store.

Default: 1771
store_idstring

Store ID for giving the exact location of the item in the store.

Default: 1771

Get Nearby Stores

getNearbyStores
Full Description

Retrieve a list of Target stores located near a specified area. Include a five-digit ZIP or postal code in the request, and optionally specify a search radius (in miles) and a result limit to control how many stores are returned. Results include store details, addresses, and operating hours. Use this tool to locate stores for availability, pickup, or delivery fulfillment planning.

Parameters

Required
placestring

5 digit Zip code/postal code to find nearby stores within the specified radius.

Optional
limitnumber

Number of nearby stores to return (default is 5).

Default: 5
withinnumber

Search radius in miles (default is 25).

Default: 25

Get Similar Items

listSimilarItems
Full Description

Retrieves items that are similar to, or frequently shopped with, the product identified by the given TCIN.

Parameters

Required
tcinsstring

Target item number (TCIN)

Optional
channelstring

Channel through which the request is made.

Default: WEB
pagestring

Page number for pagination.

Default: redsky_mcp
placement_idstring

Placement ID for the item placement context.

Default: adaptpdph3
pricing_store_idstring

Store ID for pricing information of the item at the specific store.

Default: 1771
visitor_idstring

Visitor ID for tracking user sessions.

Default: 1234

Multi Category Search Items

multiCategorySearchItems
Full Description

Target Products

  • Multi‑Category Search

Perform a multi‑category product search across Target's catalog and return a single inline "Target Products" widget. Include location metadata in the request — such as ZIP code, city, region, or latitude and longitude — to ensure results reflect accurate pricing and availability for the specified area.

When to use • The user asks for an outfit, kit, bundle, or multiple categories at once (e.g., "holiday party outfit: dress + heels + earrings"). • The user gives multiple constraints to be fanned out across categories (style, price, occasion, color, brand).

Call rules (important) • Call this tool at most once per assistant turn. • Do not call for single‑category queries ("women's black boots under $150") — use searchItems instead.

Output contract • The tool returns structuredContent for the model to reason over. • The inline UI is the source of truth for presentation; do not surface raw JSON in chat.

Parameters

Required
keywordstring

Full natural-language search query (not head terms). Do not ask clarifying questions for size/colors/styles; encode only what was said. If `raw_user_prompt` is present, `keyword` may be lightly normalized (spacing, spelling) but must preserve all details (e.g., price ceilings, styles, occasions). Examples: “boho flowy sundress under $50 for a beach trip”, “black carry-on suitcase with spinner wheels under $150”.

Optional
channelstring

Channel through which the request is made.

Default: WEB
constraintsobject

Optional structured constraints extracted from the prompt. If the user didn’t specify a facet, omit it (especially sizes and colors). Only use colors when facet_value_id is found in color_to_facet_value_map; otherwise omit colors.

countinteger

Results per page. Max 28.

Default: 24
dealsboolean

Set true when the user asks for any kind of deals. If unsure, prefer false.

Default: False
deals_typestring

Model's best interpretation of the kind of deals the user is requesting. Pick one from the provided enum list. If unsure, prefer 'unknown'.

Options:All DealsBlack FridayCircle WeekCyber MondayNew Lower PriceTarget Circle DealsWeekly AdClearanceunknown
Default: unknown
external_searchboolean

True if search is initiated from an external source.

Default: True
fan_outobject

Present for multi-category intents. Build 2–8 category-specific queries without asking questions. Avoid duplicates and carry forward constraints (e.g., under $50, boho, beach).

include_fulfillmentboolean

Include fulfillment options in the response (boolean, not string).

Default: True
intent_typestring

Model’s best interpretation of the user’s shopping intent.

Options:single_categorymulti_categoryoutfit_lookbroad_inspirationunknown
Default: unknown
is_multi_categoryboolean

Set true when the user asks for outfits/looks/gift ideas or mixes apparel + accessories (e.g., dress + sandals + sunglasses). If unsure, prefer true.

Default: False
is_multi_facetedboolean

Set true when multiple constraints are requested simultaneously (e.g., price + style + occasion).

Default: False
max_pricenumber

If there is a price range mentioned by the user, use the upper price bound in shopper currency to populate this field. If no mention of price in user query, then ignore this field.

min_pricenumber

If there is a price range mentioned by the user, use the lower price bound in shopper currency to populate this field. If no mention of price in user query, then ignore this field.

new_searchboolean

True if this is an initial typed search not modified by filters.

Default: True
offsetinteger

Zero‑based start index of the result set.

Default: 0
pagestring

Page identifier for telemetry/routing.

Default: redsky_mcp
price_rangearray

If there is a price range mentioned by the user, populate this field with the enum value that closely matches with user preference. Otherwise, ignore this field and use min_price and max_price fields respectively.

pricing_store_idstring

Store ID for pricing at a specific store.

Default: 1771
raw_user_promptstring

Verbatim copy of the user’s last message. Do not edit or paraphrase.

redirectboolean

Use this flag to indicate whether search results should follow redirects. Always set this to false to avoid receiving empty search results when a keyword matches a category search redirect.

Default: False
requested_categoriesarray

Up to 6 free‑text category names inferred from the prompt (e.g., “dresses”, “sandals”, “sunglasses”).

scheduled_delivery_store_idstring

Store ID for pricing information of the item at the specific store.

Default: 1771
sort_bystring

Sort order for search results.

Options:relevanceFeaturedPriceLowPriceHighRatingHighbestsellingnewest
Default: relevance
store_idstring

Store ID for pricing information of the item at the specific store.

Default: 1771
visitor_idstring

Visitor ID for tracking user sessions.

Default: 1234

Multiple Item Availability

multipleItemAvailability
Full Description

Fetch availability data for a set of TCINs and store ID.

Parameters

Required
channelstring
has_pricing_store_idboolean
pagestring
pricing_store_idstring
store_idstring
tcinstring
Optional
has_financing_optionsboolean
include_obsoleteboolean
is_botboolean
skip_personalizedboolean
skip_variation_hierarchyboolean
visitor_idstring

Search Items

searchItems
Full Description

Perform a single‑category catalog search and return a single inline "Target Products" widget. Include location metadata in the request — such as ZIP code, city, region, or latitude and longitude — to ensure results reflect accurate pricing and availability for the specified area. Use this call when the user query is specific to a single category. If the user query spans multiple categories, use the "multiCategorySearchItems" tool instead. When to use • The user asks about one category ("wireless earbuds", "women's black boots under $150"). • Use this to discover facets and then refine. • Supports keyword matching, pagination (offset + count), facet discovery and filtering, and channel-based result. Call rules • Call once per assistant turn. • Do not use for multi‑category or outfit/bundle intents — use multiCategorySearchItems.

Parameters

Required
keywordstring

Search term for which results have to be returned. This should be a faithful, natural‑language query that includes all constraints. If `raw_user_prompt` is present, `keyword` may be a lightly cleaned version (e.g., remove greetings) but must preserve all details.

Optional
channelstring

Channel through which the request is made.

Default: WEB
countnumber

results per page- max value of 28 is allowed

Default: 24
dealsboolean

Set true when the user asks for any kind of deals. If unsure, prefer false.

Default: False
deals_typestring

Model's best interpretation of the kind of deals the user is requesting. Pick one from the provided enum list. If unsure, prefer 'unknown'.

Options:All DealsBlack FridayCircle WeekCyber MondayNew Lower PriceTarget Circle DealsWeekly AdClearanceunknown
Default: unknown
exclude_facetsstring

Comma separated list of facet names to be excluded from the response.

Default: ALL
external_searchboolean

Indicates if this search is from an external source

Default: True
faceted_valuestring

Comma separated list of faceted values to filter the search results.

include_facetsstring

Comma separated list of facet names to be included in the response.

Default: d_categorytaxonomy,d_channel,d_deals,d_brand_all,d_rating,d_price
include_fulfillmentboolean

Flag to include fulfillment options in the response.

Default: True
max_pricenumber

If there is a price range mentioned by the user, use the upper price bound in shopper currency to populate this field. If no mention of price in user query, then ignore this field.

min_pricenumber

If there is a price range mentioned by the user, use the lower price bound in shopper currency to populate this field. If no mention of price in user query, then ignore this field.

new_searchboolean

Indicates this is an initial new typed search not modified by filters

Default: True
offsetnumber

starting number of the results set

Default: 0
pagestring

Page number for pagination.

Default: redsky_mcp
price_rangearray

If there is a price range mentioned by the user, populate this field with the enum value that closely matches with user preference. Otherwise, ignore this field and use min_price and max_price fields respectively.

pricing_store_idstring

Store ID for pricing information of the item at the specific store.

Default: 1771
redirectboolean

Use this flag to indicate whether search results should follow redirects. Always set this to false to avoid receiving empty search results when a keyword matches a category search redirect.

Default: False
scheduled_delivery_store_idstring

Store ID for pricing information of the item at the specific store.

Default: 1771
sort_bystring

Sort order for search results.

Options:relevanceFeaturedPriceLowPriceHighRatingHighbestsellingnewest
Default: relevance
store_idstring

Store ID for pricing information of the item at the specific store.

Default: 1771
visitor_idstring

Visitor ID for tracking user sessions.

Default: 1234