Media Search

Scope

• 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

• 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

Before You Search

1. First response MUST be text only: A numbered list of search sources for the user. No tool calls of any kind.
2. Wait for user to reply with their selected option number
3. Only then call the appropriate search tool (this is the FIRST tool call in the entire interaction)

• ❌ 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

• ✅ 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

Workflow Overview

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

Presenting Search Sources (First Response)

• 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

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

[NUMBER]. [SEARCH SOURCE NAME] — [Brief description]
...
[NUMBER]. Other — Provide your own URL or path

Which option would you like to use?

Examples

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

1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs
2. Search using keywords — Search Salesforce CMS by keywords and taxonomies
3. Other — Provide your own URL or path

Which option would you like to use?

search_media_cms_channels

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

1. Search using keywords — Search Salesforce CMS by keywords and taxonomies
2. Other — Provide your own URL or path

Which option would you like to use?

search_electronic_media

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

1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs
2. Other — Provide your own URL or path

Which option would you like to use?

No automated media search sources are currently configured. Please provide a direct URL or asset library path.

Executing the Selected Search Method

Search using keywords

search_media_cms_channels

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:

{
  "inputs": [{
    "searchKeyword": "keyword1 OR keyword2 OR keyword3",
    "taxonomyExpression": "{\"OR\": [\"Taxonomy1\", \"Taxonomy2\"]}",
    "searchLanguage": "en_US",
    "channelIds": "",
    "channelType": "PublicUnauthenticated",
    "contentTypeFqn": "sfdc_cms__image",
    "pageOffset": 0,
    "searchLimit": 5
  }]
}

• 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

  )

• channelIds

  : Always empty string

• channelType

  : Always

  "PublicUnauthenticated"

• contentTypeFqn

  : Always

  "sfdc_cms__image"

• pageOffset

  : Start at

  0

  , increment by

  searchLimit

  for pagination

• searchLimit

  : Default

  5

  , adjust if user requests more

{
  "inputs": [{
    "searchKeyword": "apartment OR villa OR penthouse OR residence",
    "taxonomyExpression": "{\"OR\": [\"Luxury\", \"Premium\", \"Waterfront\", \"Riverside\"]}",
    "searchLanguage": "en_US",
    "channelIds": "",
    "channelType": "PublicUnauthenticated",
    "contentTypeFqn": "sfdc_cms__image",
    "pageOffset": 0,
    "searchLimit": 5
  }]
}

{
  "inputs": [{
    "searchKeyword": "",
    "taxonomyExpression": "{\"OR\": [\"Bright\", \"Spacious\", \"Open\", \"Airy\"]}",
    "searchLanguage": "en_US",
    "channelIds": "",
    "channelType": "PublicUnauthenticated",
    "contentTypeFqn": "sfdc_cms__image",
    "pageOffset": 0,
    "searchLimit": 5
  }]
}

{
  "inputs": [{
    "searchKeyword": "car OR automobile OR vehicle OR auto",
    "taxonomyExpression": "{}",
    "searchLanguage": "en_US",
    "channelIds": "",
    "channelType": "PublicUnauthenticated",
    "contentTypeFqn": "sfdc_cms__image",
    "pageOffset": 0,
    "searchLimit": 5
  }]
}

1. Call the tool with the exact JSON payload

Search using Data 360 hybrid search

search_electronic_media

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

• User query: "modern luxury apartment with natural lighting"
• Tool call:

  search_electronic_media(searchQuery="modern luxury apartment with natural lighting")

Other (User-Provided URL)

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

Presenting Search Results

I found 4 images. Which one would you like to use?

1. Luxury Apartment Exterior
   Source: Salesforce CMS

2. Modern High-Rise Building
   Source: Salesforce CMS

3. Waterfront Residence
   Source: Salesforce CMS

4. Premium Condominium
   Source: Salesforce CMS

Applying the Selected Image

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

Search Behavior Notes

• 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

  )

• 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