Skip to main content
Glama

GoodBarber

by dev.goodbarber
OverviewDiscussionsAdmin

Create push notification

shop_create_push_notification
Destructive

Creates a shop push notification with optional user targeting, scheduling, and tap action. Guidance: Creates a shop push notification with optional user targeting, scheduling, and tap action. | context: message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendNoOptional send timing. Omit or use now for immediate sends; use at with send_at for delayed sends.
item_idNoOptional item id for section actions. For shop item actions, use only when the parent section was resolved from cms_list_cms_sections or cms_list_sections with type commerce.
messageYesMessage which will be sent to your shop app users.
send_atNoUse only when send is at. Include the MCP client user's timezone offset, for example 2026-05-28T09:30+02:00.
targetingNoOptional user IDs to target. Resolve named users by searching both customer and prospect list tools before giving up.
action_urlNoURL for action_type external_link. For section actions, provide only when a public URL or path is already known.
section_idNoSection id for action_type section; can open any resolved app or shop section. When the user names a section, first call cms_list_cms_sections with types article, photo, video, sound, maps, and agenda; if no match, call cms_list_sections with the same types plus commerce. Match titles case-insensitively and ask for an id only if nothing matches. Do not use section_id/item_id for eCommerce products.
action_typeNoOptional tap action. Omit or use open_app to open the app. Use external_link with action_url, product_url with product_slug, or section with section_id.
product_slugNoProduct slug for action_type product_url. Resolve the product from the shop catalog; the tool builds the final product page URL.
use_local_timeNoOptional, advanced. Omit it for normal scheduling; the tool converts send_at to UTC so the push fires at that instant. Set true only when the user explicitly wants delivery at the given wall-clock time in each recipient's own timezone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description discloses that the message will be sent to users and that the tool converts send_at to UTC and builds final URLs. However, it does not mention the irreversibility or side effects of sending a push notification, which is relevant given destructiveHint=true. The annotations cover the destructive nature, but the description adds only partial behavioral context.

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

Conciseness5/5

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

The description is concise, consisting of just two sentences, with the primary purpose front-loaded. It avoids unnecessary verbosity and gets straight to the point, making it easy for an agent to quickly grasp the tool's function.

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

Completeness4/5

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

Given the tool's complexity (10 parameters, nested objects, intricate resolution logic), the top-level description is brief but relies heavily on the comprehensive schema descriptions to fill in details. The combination is sufficient for an agent to understand the tool's behavior, though the description alone would be incomplete without the schema.

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 top-level description adds minimal meaning beyond the input schema; it only summarizes that targeting, scheduling, and tap action are optional. Since the schema already provides 100% coverage with detailed descriptions for all parameters, the description adds little extra value. It does not introduce new semantic clarifications beyond what is already in the property descriptions.

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 it creates a shop push notification with optional targeting, scheduling, and tap action, but it does not explicitly differentiate itself from the sibling tool shop_create_push_broadcast, which likely serves a similar purpose. The verb and resource are specific, but the absence of sibling differentiation prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus shop_create_push_broadcast or other alternatives. It focuses on internal parameter behavior (e.g., section resolution, timezone handling) but lacks explicit conditions for tool selection, leaving the agent to infer usage context.

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

All GoodBarber toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources