Skip to main content
Typed storefront tools are enabled automatically in eligible private seller conversations. No feature-flag enrollment is required.

Overview

When you ask Murph to operate your storefront — set selling terms, author a product, update operating instructions — Murph translates your request into an API call. By default it does this through a single general-purpose tool and reasons out the request shape as it goes. Typed storefront tools change that. In an eligible private seller conversation, each covered storefront operation is presented to Murph as its own tool, carrying that operation’s exact request schema. Murph sees the precise fields an operation expects before it makes the call, instead of inferring them.

What it changes for you

  • Fewer failed operations. Most tool-call errors come from the assistant guessing a field name or type. When the schema is attached to the tool, that class of error largely disappears — the request is shaped correctly the first time.
  • Same conversation. Nothing changes in how you talk to Murph. You ask for the same things in the same way; the reliability improvement happens underneath.
  • Full coverage preserved. Operations that don’t yet have a typed tool still work through the general-purpose path, so nothing you could do before stops working.
The storefront tool catalog is generally available independently of typed buyer tools, which have their own availability policy. Typed tools presented to Murph are distinct from the host-only aliases used by interactive Pages. The Teach Page uses teach_search_materials, teach_get_material, teach_save_material, and teach_renew_capability for Material listing and exact reads, seller-private URL and file additions, upload finalization, Material-owned candidate decisions, and capability renewal. MCP clients continue to use the public search, get, and save_material tools. The bridge does not permit generic Material writes or return source-access or visual-preview URLs.

Availability

The typed catalog is available automatically when Murph has an authenticated, private seller context. Shared channels retain a narrower tool surface to avoid exposing customer-specific operations, and explicitly configured evaluation sessions continue to use their supplied tool set.

Ask Murph

The assistant these tools run behind.

Playbook pricing

One of the storefront operations Murph runs for you.