Skip to main content
Glama
Sign In
Carrefour Drive MCP

Carrefour Drive MCP

by maximeallanic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_marketing_placements

Fetch advertising placements (sponsored products, banners) for a page context like home, search, or cart. Provide placement, search term, and category filters to retrieve targeted ad details with beacons and positioning data.

Instructions

Retrieves marketing/advertising placements (e.g. sponsored products, banners) for a specific placement context on Carrefour France. The placement context is determined by the URL path segment (e.g. 'home', 'home_food', 'search', 'search_cross_sell', 'search_panel', 'pdp', 'pdp_cross_sell', 'category', 'category_cross_sell', 'basket', 'checkout'). Returns a list of ad placements with product details, beacons, and positioning information.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "placement": "<placement>",
      "searchTerm": "<searchTerm>",
      "categories": "<categories>",
      "productFilters": "<productFilters>"
    },
    "name": "get_marketing_placements"
  }
}

Input Schema

NameRequiredDescriptionDefault
placementYesThe placement context to fetch marketing ads for. Examples: 'home', 'home_food', 'search', 'search_cross_sell', 'search_panel', 'pdp', 'pdp_cross_sell', 'category', 'category_cross_sell', 'basket', 'checkout'.
categoriesYesList of category names relevant to the current page context. Use an empty array for non-category placements.
searchTermYesThe search term or keyword context for the placement. Use an empty string for non-search placements (e.g. home, pdp, basket).
productFiltersYesList of product filter objects ({key, value}) to narrow placement results. Typically includes a 'Platform' filter (e.g. ['Desktop']) and optionally a 'categoryId' filter for category/PDP pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the transparency burden. It clearly states the output: 'a list of ad placements with product details, beacons, and positioning information.' This goes beyond a vague summary and sets expectations for the response structure, though it could disclose more about side effects (likely none) or session requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences deliver dense, well-structured information. The first sentence defines purpose and scope; the second details the return payload. The placement list is slightly long but serves as a quick reference and aligns with the schema. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description appropriately summarizes return contents and domain inputs. It covers the placement contexts and gives a sense of what the agent will receive. It could be more exhaustive about edge cases (e.g., what 'non-search placements' means for `searchTerm`), but the essential context is there.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and all four parameters have descriptions. The description adds value by explaining that the placement context is derived from the URL path segment and gives a comprehensive list of allowed values, which is redundant with the schema but reinforces usage. It also hints at the 'productFilters' parameter with a concrete example, enhancing understanding beyond the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Retrieves') and identifies the exact resource ('marketing/advertising placements') with clarifying examples. It also geographically scopes it to 'Carrefour France', which distinguishes it from generic ad tools among siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context is given: the tool is for placement contexts like 'home', 'search', 'pdp', etc. While it doesn't explicitly name an alternative tool for non-ad recommendations, the description's enumeration of placement contexts effectively implies when to use it. Explicit exclusions are the only thing missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools