Skip to main content
Glama

doordash_convenience_search

Search for grocery, alcohol, pharmacy, and other convenience store items using a DoorDash store ID and search query to find specific products.

Instructions

Search for items within a convenience store (grocery, alcohol, pharmacy, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesDoorDash store ID
queryYesSearch query (e.g. 'chicken breast', 'la croix')

Implementation Reference

  • Registration and handler implementation for the `doordash_convenience_search` tool, which searches for items within a convenience store.
      "doordash_convenience_search",
      {
        description:
          "Search for items within a convenience store (grocery, alcohol, pharmacy, etc.).",
        inputSchema: {
          store_id: z.string().describe("DoorDash store ID"),
          query: z
            .string()
            .describe("Search query (e.g. 'chicken breast', 'la croix')"),
        },
      },
      ({ store_id, query }) =>
        wrap(async () => {
          const items = await api.menu.searchConvenience(store_id, query);
          if (items.length === 0)
            return err(`No items found for "${query}" at this store.`);
    
          const lines = [`Search results for "${query}":\n`];
          for (const item of items) {
            lines.push(
              `- **${item.name}** ${item.price} (${item.subtext}) [ID: ${item.id}]`,
            );
          }
          lines.push(
            "\n*Use doordash_add_to_cart with store_id and item_id to add items.*",
          );
          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 full disclosure burden but only defines the domain scope (convenience store types). It fails to mention return format, pagination behavior, error cases (e.g., invalid store_id), or rate limits.

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?

Single sentence, front-loaded with the action verb, and no redundant words. However, extreme brevity leaves gaps in behavioral disclosure that could have been addressed without sacrificing clarity.

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

Completeness3/5

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

Given the simple 2-parameter input schema and lack of output schema, the description meets minimum viability by establishing the tool's domain. However, it should ideally hint at return values or the prerequisite workflow given zero annotation coverage.

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?

Schema description coverage is 100% (both store_id and query are fully documented in the schema with examples). The description adds no parameter-specific guidance, which aligns with the baseline score for high schema 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 uses specific verb 'Search' and resource 'items within a convenience store', clearly distinguishing from the general 'doordash_search' sibling by specifying the convenience retail domain (grocery, alcohol, pharmacy). However, it doesn't explicitly contrast with restaurant/menu search tools.

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 guidance provided on when to use this versus the general 'doordash_search' tool, nor does it mention that 'store_id' must be obtained beforehand (likely via the general search). No prerequisites or alternatives are documented.

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