create_address

Swiggy (Instamart/Food): Create a new delivery address for the authenticated user.

Example

const result = await client.callTool({
  name: "create_address",
  arguments: {
    fullAddress: "...",
    addressLine: "...",
    addressLine2: "...",
    city: "Bengaluru",
    postalCode: "...",
    addressCategory: "HOME",
    userName: "...",
    userPhone: "...",
  },
});

Parameters

Session credentials (user identity, access token) are supplied automatically by the authenticated MCP session - you do not pass them in the tool call. See Authenticate.

Response

Success:

{
  "success": true,
  "data": { "addressId": "addr_new_123" },
  "message": "Address created successfully"
}

• data.addressId — use this directly in subsequent calls (search_products, get_cart, update_cart, checkout). No need to call get_addresses again.

On failure:

{
  "success": false,
  "error": { "message": "description of what went wrong" }
}

See Error codes for the full catalogue.

Output schema

data: {
  addressId: string;
}

This schema documents the structured payload returned by create_address. addressId is the stable identifier for the saved address; use it in subsequent cart, checkout, and payment calls. Latitude and longitude are optional and are geocoded server-side when omitted.

Generally available: As of Aug 2026, create_address is available to every authenticated Swiggy user — no whitelist or feature flag. Latitude and longitude are optional; the server geocodes from the address (via the address-recommendations service) when they are omitted.

Details

Agent guidance

How Swiggy agents and orchestration logic use this tool. Surface these expectations in your prompts or tool-selection policies.

**WORKFLOW **- What to ASK the user:

1. Ask: "What is your complete delivery address?" (Get the full address as a single string)
2. Ask: "What is your name?"
3. Ask: "What is your phone number?"
4. Ask: "What type of address is this?" (Options: HOME, WORK, OFFICE, FRIENDS_AND_FAMILY, or OTHER)
5. Ask (optional): "Would you like to give a name/label to this address?" (e.g., "My Home", "Office")
6. Ask: "Is this address for you or someone else?"
   • If for someone else: Ask for the receiver's name and phone number
7. (Optional) If the user provides latitude/longitude, include them — otherwise the server will geocode from the address automatically.

**AUTOMATIC PARSING **- What YOU must do (DO NOT ask user for these): After getting the full address, YOU must automatically parse it and extract:

• addressLine: Main street/building/house number (REQUIRED - extract from full address)
• addressLine2: Apartment/floor/wing/additional details (REQUIRED - extract from full address)
• city: City name (REQUIRED - extract from full address)
• postalCode: Postal/ZIP code (REQUIRED - extract from full address)
• locality: Area/neighborhood (optional - extract if available)

• NEVER ask the user to provide addressLine, addressLine2, city, or postalCode separately
• YOU parse the full address and extract these components automatically
• The user provides: full address, name, phone, address type, optional tag, and receiver details if applicable
• Latitude and longitude are optional — do NOT ask the user for coordinates unless they volunteer them. The server geocodes from the address when omitted
• Account details (userName, userPhone) are ALWAYS the authenticated user
• Receiver details (receiverName, receiverPhone) are only used when delivering to someone else

Next in this journey →

Continue with search_products.