How do I get Criteo Retail Media API credentials?

Log in to the Criteo Developer Portal, create a new app specifically for Retail Media, and you will receive a Client ID and Client Secret.

What is the difference between Marketing and Retail Media APIs?

Marketing API focuses on off-site display and retargeting, while Retail Media API is designed for managing sponsored products and on-site advertising within retailer platforms.

Can I see keyword performance?

Yes, you can use the list_line_item_keywords tool to see which keywords are being targeted and request reports to see their conversion metrics.

Criteo Retail Media API MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Criteo Retail Media API
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Criteo Retail Media API through the Vinkius — pass the Edge URL in the `mcps` parameter and every Criteo Retail Media API tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Criteo Retail Media API Specialist",
    goal="Help users interact with Criteo Retail Media API effectively",
    backstory=(
        "You are an expert at leveraging Criteo Retail Media API tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Criteo Retail Media API "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Criteo Retail Media API MCP Server

Integrate the Criteo Retail Media API directly into your AI workflow. Manage your retail advertising campaigns, monitor line item performance, and track product data across your retailer and advertiser accounts using natural language.

When paired with CrewAI, Criteo Retail Media API becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Criteo Retail Media API tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Retail Campaign Management — List and retrieve detailed settings for all your retail media campaigns.
Line Item Monitoring — Access real-time configuration and performance for your retail line items.
Retailer & Product Discovery — Explore retail partners and products associated with your advertiser accounts.
Keyword & Performance Insights — Audit targeted keywords and request performance reports via chat.

The Criteo Retail Media API MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Criteo Retail Media API to CrewAI via MCP

Follow these steps to integrate the Criteo Retail Media API MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Criteo Retail Media API

Why Use CrewAI with the Criteo Retail Media API MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Criteo Retail Media API through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Criteo Retail Media API + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Criteo Retail Media API MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Criteo Retail Media API for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Criteo Retail Media API, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Criteo Retail Media API tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Criteo Retail Media API against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Criteo Retail Media API MCP Tools for CrewAI (10)

These 10 tools become available when you connect Criteo Retail Media API to CrewAI via MCP:

get_retail_campaign_details

Get detailed settings for a specific retail campaign

get_retail_media_report

Request a performance report for retail media

list_account_products

List products associated with a specific retail account

list_advertiser_accounts

List advertiser accounts managed in retail media

list_line_item_keywords

List keywords targeted by a specific line item

list_line_items

List all line items (ad groups) for retail campaigns

list_retail_budgets

List active budgets for retail media campaigns

list_retail_campaigns

List all retail media campaigns in Criteo

list_retailers

List retail partners available in your account

search_retail_campaigns_by_name

Search for retail campaigns by name keyword

Example Prompts for Criteo Retail Media API in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Criteo Retail Media API immediately.

"List all retail media campaigns for advertiser account 'a8s9df7'."

"Show me the keywords being targeted in line item 'l123abc'."

"Get a performance report for all retail campaigns from yesterday."

Troubleshooting Criteo Retail Media API MCP Server with CrewAI

Common issues when connecting Criteo Retail Media API to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Criteo Retail Media API + CrewAI FAQ

Common questions about integrating Criteo Retail Media API MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.