Skip to main content
Glama

doordash_create_group_order

Create a group order at a DoorDash restaurant to coordinate food delivery with multiple people, generating a shareable link for participants to join and add items.

Instructions

Create a group order at a restaurant. Returns a share link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesDoorDash store ID

Implementation Reference

  • Registration and implementation handler for the 'doordash_create_group_order' tool in src/tools/index.ts.
    server.registerTool(
      "doordash_create_group_order",
      {
        description:
          "Create a group order at a restaurant. Returns a share link.",
        inputSchema: {
          store_id: z.string().describe("DoorDash store ID"),
        },
      },
      ({ store_id }) =>
        wrap(async () => {
          const menu = await api.menu.getStoreMenu(store_id);
          const result = await api.group.createGroupCart(store_id, menu.menuId);
    
          const lines = [
            `# Group Order Created: ${menu.name}\n`,
            `**Share link:** ${result.shareUrl}`,
            `**Cart ID:** ${result.id}`,
            `**Type:** Creator pays for all\n`,
            "Send the share link to others.",
            "Use `doordash_group_order_status` to see everyone's items.",
            "Use `doordash_checkout` with this cart to place the order.",
          ];
          return ok(lines.join("\n"));
        }),
    );
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. While it mentions the share link return value (helpful given no output schema), it omits critical side effects: whether this initializes an empty cart, if there's an expiration timer, authentication requirements, or that participants must use the link to join before checkout.

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?

Extremely concise at two sentences with no redundancy. However, given the lack of annotations and output schema, the brevity borders on under-specification rather than efficient communication, warranting a slight deduction.

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?

For a group ordering workflow (moderately complex domain), the description is insufficient. It fails to explain the group order lifecycle, how invitees interact with the share link, or the relationship to cart/checkout tools. The mention of 'share link' partially compensates for missing output schema but leaves operational context gaps.

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 input schema has 100% description coverage for the single 'store_id' parameter. The description adds no additional semantic context (e.g., format examples, how to obtain the ID), meeting the baseline for high-coverage schemas.

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 ('Create') and resource ('group order'), distinguishing it from regular orders via the sibling tool 'doordash_place_order'. The mention of returning a 'share link' clarifies the collaborative output nature, though it doesn't explicitly contrast with 'doordash_join_group_order'.

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?

No explicit guidance on when to use this versus placing a regular order or joining an existing group order. The description implies it's for creating new collaborative sessions but doesn't state prerequisites (e.g., needing to add items afterward) or workflow sequencing.

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

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