Skip to main content
Glama

⚠️ Orders: select courier slot

orders_set_courier_delivery_range

Books a courier pickup time slot for an order using seller's address and contact details. Updates the slot if courier hasn't picked up yet.

Instructions

⚠️ Selects (books) a specific time slot for a courier to pick up the item (set_courier_delivery_range), for seller-courier delivery. A write operation, unlike the read method orders_get_courier_delivery_range, which only shows the available slots — call it first and take the interval and intervalType from the response. Can be called again to change the time while the courier has not yet picked up the parcel. The response contains a success flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesAvito order ID.
addressYesSeller's address where the courier picks up the item.
addressDetailsNoSeller address details (entrance, floor, apartment, etc.).
nameYesFull name of the seller's contact person.
phoneYesPhone of the seller's contact person.
startDateYesStart date/time of the courier arrival in date-time format (ISO 8601); taken from the get method response.
endDateYesEnd date/time of the courier arrival in date-time format (ISO 8601); taken from the get method response.
intervalTypeYesInterval type: fixed (fixed slot) or asap (as soon as possible). Taken from the orders_get_courier_delivery_range response.
dryRunNov0.7.0: if true — returns a preview of the HTTP request without calling the Avito API. Safe for inspecting exactly what would be done. Default: the value of AVITO_MCP_DRY_RUN_DEFAULT (usually false).
idempotencyKeyNov0.7.0: optional key for duplicate protection. A repeat call with the same key within AVITO_MCP_IDEMPOTENCY_TTL_SEC returns the cached result. The same key with different args returns a conflict error — this is safe by design.
Behavior4/5

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

Annotations already indicate write operation and non-destructive. Description confirms it is a write operation and adds that response contains a success flag. Discloses ability to change time before pickup.

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?

Three sentences front-loaded with purpose, no fluff. Warning icon draws attention. Perfectly concise.

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?

For a tool with 10 parameters and no output schema, description covers workflow, ties to read method, and mentions success flag. Adequate completeness.

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 covers all parameters. Description adds value by explaining that startDate, endDate, and intervalType come from the get method, and briefly explains dryRun and idempotencyKey.

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?

Description states 'Selects (books) a specific time slot for a courier to pick up the item' with clear verb and resource, and distinguishes from sibling orders_get_courier_delivery_range.

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?

Explicitly tells to call the read method first and take parameters from its response, and that it can be called again to change time. Provides clear context but does not explicitly state when not to use.

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

Install Server

Other Tools

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/elchin92/avito-mcp'

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