Skip to main content
Glama

Delivery: change parcel [sandbox v1]

delivery_v1_change_parcel

Queue a request to change a test parcel's details, such as receiver info or storage options. Use for one parcel; poll another endpoint for outcome.

Instructions

[SANDBOX v1] Creates a request to change ONE test parcel's data (e.g. the receiver's name/phone), per the type enum (changeReceiver / prohibitParcelReceive / extendParcelStorage / prohibitParcelAcceptance). The call only QUEUES the request — poll delivery_v1_get_change_parcel_info for the outcome. For bulk changes use delivery_change_parcels instead. Sandbox-only, for delivery-service PARTNERS.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parcelIDYesIdentifier of the test parcel to change.
typeYesRequest type. Enum: changeReceiver | prohibitParcelReceive | extendParcelStorage | prohibitParcelAcceptance.
applicationNoChange-request data (depends on type, optional).
optionsNoAdditional request options (optional).
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 provide readOnlyHint=false but no other behavioral hints. The description adds key context: the tool queues the request (async behavior), is sandbox-only, and requires polling. No contradictions.

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 concise sentences. Front-loaded with purpose, then async behavior, alternative, and constraints. No fluff.

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?

Covers main aspects: async nature, alternative for bulk, sandbox/partner restriction, enum values. The application and options fields have schema descriptions. Output is not described but refers to polling another tool. Good for a tool with 6 params and no output schema.

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%, so baseline is 3. The description adds value by listing the type enum values and explaining the queue/poll flow. It also mentions dryRun and idempotencyKey but these are already in schema.

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 specifies the verb 'creates a request' and the resource 'ONE test parcel's data', clearly distinguishing from the sibling tool 'delivery_change_parcels' for bulk changes.

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

Usage Guidelines5/5

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

Explicitly states when to use (single parcel changes) and when not (bulk changes use delivery_change_parcels). Also specifies sandbox-only, partner restriction, and that the call only queues the request, requiring polling of another tool.

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