Skip to main content
Glama
yasmanmesa
by yasmanmesa

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
YANDEX_EATS_DRY_RUNNoIf 'true', tools do not call the APIfalse
YANDEX_EATS_BASE_URLNoBase URL for API (default: https://dc-partner.eda.yandex.net)https://dc-partner.eda.yandex.net
YANDEX_EATS_CLIENT_IDYesOAuth client id
YANDEX_EATS_TIMEOUT_MSNoTimeout in milliseconds (default: 30000)30000
YANDEX_EATS_PARTNER_NAMENoSent as Partner-Name header (required for several write tools)
YANDEX_EATS_CLIENT_SECRETYesOAuth client secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
yandex_eats_auth_statusA

Check whether Yandex Eats Vendor Management credentials are configured and whether a cached OAuth token is valid. Never returns the access token.

yandex_eats_refresh_tokenA

Force-refresh the OAuth2 client-credentials token from POST /oauth2/token on dc-partner.eda.yandex.net. Does not return the token.

yandex_eats_orders_historyA

Fetch order history from Vendor Management (POST /v1/orders-history). Limits: max 1000 orders in the response; history retained for the last 180 days. Status filter values are NEW, CANCELLED, DELIVERED.

yandex_eats_orders_detailsA

Fetch detailed information for orders by Yandex eats_id list (POST /v1/get-orders-details). Max 100 ids per request; history retained 180 days. eats_id format: DDDDDD-DDDDDDDD.

yandex_eats_busy_mode_statusB

List restaurants with active high-demand (busy) status (POST /partner-integration/v1/place-info/v1/busy-mode-status). High demand adds extra cooking minutes.

yandex_eats_block_statusC

Get restaurant block status from Vendor Management (POST /v2/status). Requires Partner-Name.

yandex_eats_block_placesA

Block restaurant(s) in Yandex Eats (POST /block). Destructive. Requires confirm=true and Partner-Name. Tags: technical_problem | too_busy. If 'to' is omitted, block is indefinite.

yandex_eats_unblock_placesA

Unblock restaurant(s) (POST /unblock). Destructive. Requires confirm=true, Partner-Name, and blockIds from a prior block/status response.

yandex_eats_menu_importA

Force Yandex to re-parse the partner menu or stop-list (POST /menu/import/initiation). Requires Partner-Name. operationType: menu (default) or menu_stop_list. Safe to retry if unsure whether import started.

yandex_eats_validate_courier_codeB

Validate the courier pickup code for an order (POST /platform/orders/{orderId}/codes/validate). Requires Partner-Name. Sensitive operational tool.

yandex_eats_feedback_answerA

Reply to customer order feedback with text and optional promo percent (POST /feedback-answer). Subscription-gated — may return 403 without subscription. Promo values: 10, 15, 20, 30, 40.

Prompts

Interactive templates invoked by user choice

NameDescription
yandex_eats_investigate_orderPlaybook to look up order history/details for a place and eats_id
yandex_eats_resync_menuPlaybook to force a menu or stop-list import for a restaurant

Resources

Contextual data attached and managed by the client

NameDescription
overviewCapabilities and configuration summary
config-statusNon-secret configuration and token cache status

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yasmanmesa/yandex-eats-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server