Skip to main content
Glama

update_delivery

Modify delivery details like addresses, times, or contact information for DoorDash orders to correct errors or adjust arrangements.

Instructions

Update delivery details such as addresses, times, or other parameters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
external_delivery_idYesThe delivery ID to update
pickup_addressNoNew pickup address
pickup_business_nameNoNew pickup business name
pickup_phone_numberNoNew pickup phone number
pickup_instructionsNoNew pickup instructions
dropoff_addressNoNew dropoff address
dropoff_business_nameNoNew dropoff business name
dropoff_phone_numberNoNew dropoff phone number
dropoff_instructionsNoNew dropoff instructions
dropoff_contact_given_nameNoDropoff contact first name
dropoff_contact_family_nameNoDropoff contact last name
contactless_dropoffNoWhether delivery should be contactless
tipNoThe tip amount in cents
order_valueNoUpdated order value in cents
pickup_timeNoPreferred pickup time (ISO-8601 format)
dropoff_timeNoPreferred dropoff time (ISO-8601 format)
dropoff_requires_signatureNoWhether dropoff requires signature
dropoff_cash_on_deliveryNoCash to collect on delivery in cents

Implementation Reference

  • The handler function for the 'update_delivery' tool. It destructures the arguments to separate the external_delivery_id and passes the rest as updateArgs to the DoorDash client's updateDelivery method.
    handler: (client, args) => {
      const { external_delivery_id, ...updateArgs } = args;
      return client.updateDelivery(external_delivery_id, updateArgs);
    },
  • Input schema for the update_delivery tool, specifying all possible parameters that can be updated for a delivery.
    inputSchema: {
      type: 'object',
      properties: {
        external_delivery_id: { type: 'string', description: 'The delivery ID to update' },
        pickup_address: { type: 'string', description: 'New pickup address' },
        pickup_business_name: { type: 'string', description: 'New pickup business name' },
        pickup_phone_number: { type: 'string', description: 'New pickup phone number' },
        pickup_instructions: { type: 'string', description: 'New pickup instructions' },
        dropoff_address: { type: 'string', description: 'New dropoff address' },
        dropoff_business_name: { type: 'string', description: 'New dropoff business name' },
        dropoff_phone_number: { type: 'string', description: 'New dropoff phone number' },
        dropoff_instructions: { type: 'string', description: 'New dropoff instructions' },
        dropoff_contact_given_name: { type: 'string', description: 'Dropoff contact first name' },
        dropoff_contact_family_name: { type: 'string', description: 'Dropoff contact last name' },
        contactless_dropoff: { type: 'boolean', description: 'Whether delivery should be contactless' },
        tip: { type: 'number', description: 'The tip amount in cents' },
        order_value: { type: 'number', description: 'Updated order value in cents' },
        pickup_time: { type: 'string', description: 'Preferred pickup time (ISO-8601 format)' },
        dropoff_time: { type: 'string', description: 'Preferred dropoff time (ISO-8601 format)' },
        dropoff_requires_signature: { type: 'boolean', description: 'Whether dropoff requires signature' },
        dropoff_cash_on_delivery: { type: 'number', description: 'Cash to collect on delivery in cents' },
      },
      required: ['external_delivery_id'],
    },
  • index.js:130-161 (registration)
    The complete tool registration object for 'update_delivery' in the TOOLS array, which is used by the MCP server for listing and executing tools.
    {
      name: 'update_delivery',
      description: 'Update delivery details such as addresses, times, or other parameters',
      inputSchema: {
        type: 'object',
        properties: {
          external_delivery_id: { type: 'string', description: 'The delivery ID to update' },
          pickup_address: { type: 'string', description: 'New pickup address' },
          pickup_business_name: { type: 'string', description: 'New pickup business name' },
          pickup_phone_number: { type: 'string', description: 'New pickup phone number' },
          pickup_instructions: { type: 'string', description: 'New pickup instructions' },
          dropoff_address: { type: 'string', description: 'New dropoff address' },
          dropoff_business_name: { type: 'string', description: 'New dropoff business name' },
          dropoff_phone_number: { type: 'string', description: 'New dropoff phone number' },
          dropoff_instructions: { type: 'string', description: 'New dropoff instructions' },
          dropoff_contact_given_name: { type: 'string', description: 'Dropoff contact first name' },
          dropoff_contact_family_name: { type: 'string', description: 'Dropoff contact last name' },
          contactless_dropoff: { type: 'boolean', description: 'Whether delivery should be contactless' },
          tip: { type: 'number', description: 'The tip amount in cents' },
          order_value: { type: 'number', description: 'Updated order value in cents' },
          pickup_time: { type: 'string', description: 'Preferred pickup time (ISO-8601 format)' },
          dropoff_time: { type: 'string', description: 'Preferred dropoff time (ISO-8601 format)' },
          dropoff_requires_signature: { type: 'boolean', description: 'Whether dropoff requires signature' },
          dropoff_cash_on_delivery: { type: 'number', description: 'Cash to collect on delivery in cents' },
        },
        required: ['external_delivery_id'],
      },
      handler: (client, args) => {
        const { external_delivery_id, ...updateArgs } = args;
        return client.updateDelivery(external_delivery_id, updateArgs);
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool updates delivery details, implying a mutation operation, but lacks critical information: whether this requires specific permissions, if updates are reversible, what happens to unspecified fields (partial vs. full updates), error handling, or rate limits. The description is too vague for a mutation tool with 18 parameters.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words and directly states what the tool does. However, it could be slightly more structured by explicitly listing key parameter categories (e.g., 'Update delivery details including addresses, contact info, timing, and payment parameters').

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

Completeness2/5

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

Given the complexity (18 parameters, mutation operation) and lack of annotations or output schema, the description is incomplete. It doesn't explain the update behavior (e.g., partial updates allowed?), permissions needed, error conditions, or what the tool returns. For a tool with many parameters and no structured output, more context is required to guide effective use.

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

Parameters3/5

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

The description mentions 'addresses, times, or other parameters', which loosely maps to some input schema fields (e.g., pickup/dropoff addresses, pickup/dropoff times). However, with 100% schema description coverage, all parameters are already documented in the schema. The description adds minimal value beyond what the schema provides, meeting the baseline of 3 for high coverage.

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

Purpose4/5

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

The description clearly states the action ('Update') and resource ('delivery details'), specifying the types of details that can be modified (addresses, times, or other parameters). It distinguishes itself from siblings like 'create_delivery' or 'cancel_delivery' by focusing on updates, but doesn't explicitly differentiate from potential overlap with other update-related tools that might exist.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., that a delivery must exist), conditions for use (e.g., only before delivery starts), or comparisons to sibling tools like 'create_delivery' or 'get_delivery'. Usage is implied by the verb 'update', but explicit context is missing.

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/amannm/doordash-mcp'

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