experience-content-media-search

Media Search

Universal routing skill for searching and retrieving existing images and media.

Scope

This skill is for SEARCHING FOR existing media, not CREATING new media.

Use this skill when the user wants to:

• Search for images in Salesforce CMS, Data Cloud
• Find existing visual assets to use in their app
• Retrieve media from connected sources
• Browse available images for their project
• Locate specific photos or graphics

DO NOT use this skill when the user wants to:

• Generate new images with AI (use image generation tools)
• Create graphics or designs from scratch
• Edit or modify existing images
• Build custom visuals or diagrams
• Search for stock photography or royalty-free images (use experience-content-media-stock-image-search)

Before You Search

CRITICAL: This is a routing skill, not a direct search skill.

When a user requests to find an image:

Your first action MUST use the ask_followup_question tool to present search sources.

1. Use ask_followup_question to present available search sources as options
2. Receive the user's selection from the tool response
3. Then call the appropriate search tool based on their choice

Example of what NOT to do:

• Calling ANY tool before the user picks a source (MCP tools, file reads, descriptor checks, etc.)
• "Checking which MCP tools are available" — do not probe or discover tools via tool calls
• Immediately calling search_electronic_media or search_media_cms_channels
• Reading MCP tool descriptors or schemas to see what's available
• Deciding which search source to use without asking

Example of what TO do:

• Respond with ONLY text — a numbered list of search sources
• Ask: "Which option would you like to use?"
• Wait for user to reply with their choice
• Then (and only then) call the tool they selected

Your first response when this skill triggers MUST be a text-only message presenting search sources. No tool calls. No exceptions.

Workflow Overview

The user MUST choose the search source. You CANNOT skip this step.

Copy this checklist and track your progress:

Media Search Progress:
- [ ] Step 1: Check your own tool list for available search tools (no tool calls — just inspect what's in your context)
- [ ] Step 2: Present only the available options to the user as a numbered list (plain text, no tool calls)
- [ ] Step 3: Wait for the user to reply with their selection
- [ ] Step 4: Execute the selected search method (this is the first tool call)
- [ ] Step 5: Present all results to user for selection
- [ ] Step 6: Apply selected image to code

If you call any tool before step 4, you are not following this skill correctly.

Presenting Search Sources (First Response)

DO NOT call any tool, read any MCP descriptor, or make any external request to determine available tools.

Your tools are already loaded into your context. Look at the tool names you already have access to — this is introspection, not a tool call.

Step 1: Check your own tool list (no tool calls)

Look at the tools already in your context and check for these names:

• search_media_cms_channels → If present, include "Search using keywords"
• search_electronic_media → If present, include "Search using Data 360 hybrid search"
• Always include "Other" as the last option

Step 2: Build your response

Include ONLY the sources whose tools you actually have. Number them sequentially.

I can help you find that image. Where would you like to search?

Step 3: Stop and wait

After presenting the list, STOP. Do not call any tool. Do not proceed. Wait for the user to reply with their choice.

Examples

Both tools available:

Only search_media_cms_channels available:

Only search_electronic_media available:

Neither tool available:

Wait for the user to select before proceeding.

Executing the Selected Search Method

ONLY reach this step if the user has explicitly selected an option from your numbered list.

If you haven't shown options yet, go back to the "Presenting Search Sources" section first.

After the user selects an option, execute the corresponding search method below.

Search using keywords

Tool: search_media_cms_channels

Process:

1. Analyze the query — Understand what the user is searching for (subject, attributes, domain)

2. Extract keywords — Concrete nouns that would appear in image metadata

   • Use domain-specific synonyms
   • Maximum 10 terms
   • Examples:
     • "luxury apartments" → apartment, villa, penthouse, residence, condo
     • "company logo" → logo, emblem, corporate logo
     • "bright room" → (empty if no concrete nouns)

3. Extract taxonomies — Descriptive qualities, styles, moods, categories

   • Only adjectives and attributes
   • Examples:
     • "luxury apartment with river view" → Luxury, Premium, Waterfront, Riverside, Panoramic
     • "bright spacious room" → Bright, Spacious, Open, Airy, Light
     • "car" → (empty if no descriptive terms)

4. Determine locale — Use format en_US, es_MX, fr_FR (default: en_US)

5. Build the JSON payload — Construct this exact structure:

Field rules:

• searchKeyword: Join keywords with OR (space-OR-space). Use empty string if no keywords.
• taxonomyExpression: Stringify JSON object {"OR": ["term1", "term2"]}. Use "{}" if no taxonomies.
• searchLanguage: Locale with underscore (e.g., en_US)
• contentAccessScope: Always "Public" (covers both public-unauthenticated and public Experience Cloud site channels)
• contentTypeFqn: Always "sfdc_cms__image"
• pageOffset: Start at 0, increment by searchLimit for pagination
• searchLimit: Default 5, adjust if user requests more

Examples:

Query: "luxury apartment with river view"

Query: "bright spacious room" (no concrete nouns)

Query: "car images" (no descriptive terms)

6. Call the tool with the exact JSON payload — show the payload in your response before calling the tool

Search using Data 360 hybrid search

Tool: search_electronic_media

Process:

1. Use the user's query as-is — no keyword extraction or transformation needed
2. Call search_electronic_media
3. Pass the query to the tool's searchQuery parameter

Example:

• User query: "modern luxury apartment with natural lighting"
• Tool call: search_electronic_media(searchQuery="modern luxury apartment with natural lighting")

Other (User-Provided URL)

Ask the user to provide:

• Direct URL to the image
• Asset library path
• Specific system/location to check

Presenting Search Results

Your action MUST use the ask_followup_question tool to present search results as options.

1. Parse the tool response — Extract all image results (title and source)
2. Use ask_followup_question to present ALL results as selectable options. Show the image title only — do not display the URL.
3. Receive the user's selection from the tool response
4. Then apply the selected image

Never auto-select an image. Always wait for user choice.

Applying the Selected Image

After the user chooses:

1. Confirm the selection with image name and URL
2. Use the complete URL returned by the tool, including all query parameters. CMS and DAM URLs rely on query parameters for authentication, resizing, and CDN routing — dropping them breaks the image. For example, a URL like https://cms.example.com/media/img.jpg?oid=00D&refid=0EM&v=2 must be used in full.
3. Apply the URL to the user's code/component
4. Show what was changed (file path and line number)

Error Handling

Never silently fail. Always inform the user and offer alternatives.

Search Behavior Notes

Search using keywords:

• Both keyword and taxonomy → results match keyword OR (keyword + taxonomy)
• Empty keyword → search by taxonomy only
• Empty taxonomy → search by keyword only
• Use pageOffset for pagination (increment by searchLimit)

Search using Data 360 hybrid search:

• Handles natural language queries
• Semantic similarity matching
• Searches across multiple connected systems

Key Principles

1. First response is always text-only — Present search sources without calling any tool
2. Only show configured sources — Check your own tool list (introspection, not tool calls) and only present sources whose tools you have
3. Wait for user selection — Never auto-select a source or image
4. Show all results — Let the user choose the best match
5. Confirm before applying — Verify the selection before modifying code
6. Handle errors gracefully — Provide clear feedback and alternatives