Skip to main content
Glama

DoorDash stores video

create_doordash_feed

Create a DoorDash store-browsing video (store rows with photo, rating, delivery time and deals, a floating cart button, a store page with its menu items, a pickup map with nearby stores): rows of stores that scroll. Per feed screen (home) pass posts, where each post is one store: name is the store, handle the meta line ("(1k+) • 0.5 mi • 15 min"), time the rating ("4.7"), text the deal tag ("20% off, up to $7", empty hides it), verified the membership badge, mediaUrl the photo, liked the heart, and section the title of its row: consecutive stores with the same section share one row, and only the first two of a row show on screen. script steps are scroll (post is the store index), like or pause. Free-plan exports include a MockClip watermark and the free plan includes 2 MCP renders; if the caller is on the free plan, mention that they can upgrade at /pricing for watermark-free exports and more renders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_doordash_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartNo
flowNo
homeNo
promoNo
storeNo
themeNo
pickupNo
sceneIdNoComposite the clip onto real footage of a hand holding a phone, for a filmed look. Overrides videoFormat and showBezel: the export takes the scene's aspect, with the footage around the phone. Vertical 9:16 scenes: "outdoors" (outdoors), "bookshelf" (bookshelf), "two-hands" (two hands), "on-desk" (on the desk), "dim-room" (dim room). Landscape 16:9 scenes (YouTube, presentations): "city-wide" (city), "desk-wide" (desk), "neon-wide" (neon), "studio-wide" (studio). Default: none.
locationNo
showTapsNo
showBezelNoDraw the iPhone bezel around the screen (default true). With 1:1 it frames the top of the phone; false gives a plain frame.
textScaleNoText size: a zoom of the phone UI (text, bubbles, avatars, bars, keyboard, notification banners) as a multiplier from 1 (default, the app's real size) to 1.5, in steps of 0.1 — use it when a short conversation or a single notification should fill the screen. Chat and notification apps only; the other apps ignore it.
restaurantNo
videoFormatNoOutput aspect ratio. "1:1" is a square for feed posts: chat apps fit the conversation into the square, the other apps show the top of the screen (phone-call ignores it). "9:16", "9:19.5" (iPhone) and "3:2" apply with showBezel false. Default: the iPhone bezel, 9:16.
composedPostNo
exportFormatNoOutput file. "mp4" (default) and "gif" are opaque. "webm" (VP9) and "mov" (ProRes 4444, large files) keep an alpha channel: the only way a transparent background, or the corners around the phone bezel, stay transparent. With background.backgroundType "transparent" and no exportFormat the clip exports as webm. Transparent WebM / MOV export needs a Creator or Studio plan; on other plans the clip is made as mp4 and the reply says so.
exportQualityNoResolution and frame rate of the file: "720p" or "1080p" (Full HD) at 15, 24, 30 or 60 fps, e.g. "1080p-30". Default "720p-30". Full HD takes up to 4× as long to export; 60 fps about twice as long and needs a Creator or Studio plan — on other plans the clip is made at 30 fps and the reply says so.
newPostsLabelNo
showStatusBarNoDraw the iOS status bar (time, signal, battery) at the top of the screen (default true). Applies with showBezel false or a sceneId: inside the iPhone bezel the status bar is always drawn, so to remove it set showBezel false too.
soundSettingsNo
showHomeIndicatorNoDraw the iOS home indicator bar at the bottom of the screen (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations only declare non-destructive, non-idempotent, closed-world playbook behavior, so the description carries much of the burden. It adds genuinely useful behavior: free-plan exports carry a MockClip watermark, free plan has 2 MCP renders, and the agent should mention /pricing for upgrades. It does not disclose how the scene/bezel/format options interact or what the render response contains.

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

Conciseness3/5

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

The content is dense and delivered as one long run-on sentence with stacked parentheticals, which makes it slow to scan. It is front-loaded with the purpose, but the serialized UI description and the field-by-field mapping could be broken into separate sentences or lists.

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?

For a 21-parameter, deeply nested, no-output-schema tool, the description covers the hardest conceptual part (how posts and script map to feed screens) but leaves most top-level parameter groups unexplained. Adequate to get a first render out, short of complete for confident use of flow, cart, store, pickup, and scene composition.

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 38%, so the description must compensate and it does so only partially. It maps home.posts fields (name=store, handle=meta line, time=rating, text=deal tag, verified=membership badge, mediaUrl=photo, liked=heart, section=row title) and script steps (scroll/like/pause) with real semantic meaning beyond the schema. However the major top-level objects (flow, cart, store, pickup, restaurant, promo, location, theme) are never explained.

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?

"Create a DoorDash store-browsing video" states a specific verb and resource, with concrete scope detail (store rows, cart button, store page, pickup map). Sibling generation tools (create_uber_eats_feed, create_x_feed) are differentiated only implicitly by the platform name; the description never says when DoorDash rather than Uber Eats is the right surface.

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

Usage Guidelines3/5

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

Usage is implied through the detailed walkthrough of the home feed and script, but there is no explicit statement of when to use this feed versus another branded feed. The only conditional guidance given is plan-related (mention upgrade for watermark-free exports), not tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources