Skip to main content
Glama
UVU-Store

shopify-graphql-mcp

by UVU-Store

create_marketing_engagement

Create a marketing engagement to track customer interactions for a marketing activity or channel, recording clicks, impressions, conversions, sales, and orders to measure performance.

Instructions

Create a marketing engagement for a marketing activity or channel. Tracks customer interactions like clicks, impressions, conversions, sales, and orders. Requires write_marketing_events scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ordersNoNumber of orders generated
remoteIdNoA custom unique identifier for the marketing activity. Either this or marketingActivityId should be set for activity-level engagements.
utcOffsetYesThe UTC offset for the time zone in which the metrics are being reported (format: '+HH:MM' or '-HH:MM', e.g., '-07:00')
failsCountNoTotal number of fails (bounced emails/messages)
occurredOnYesThe calendar date for which the metrics are being reported (ISO 8601 format, e.g., '2018-06-29')
sendsCountNoTotal number of marketing emails or messages sent
viewsCountNoTotal number of views (email opens, video plays)
clicksCountNoTotal number of interactions/clicks on the marketing content
salesAmountNoAmount of sales generated from the marketing content
sharesCountNoTotal number of times content was shared or reposted
isCumulativeYesWhether metrics have been aggregated from the first day of reporting up to occurredOn (true) or aggregated over a single day (false). Non-cumulative is preferred.
adSpendAmountNoThe total ad spend amount for the marketing content
channelHandleNoThe unique string identifier of the channel for channel-level engagements. Set when providing channel-level engagements only.
commentsCountNoTotal number of comments on the marketing content
sessionsCountNoNumber of online store sessions generated
favoritesCountNoTotal number of favorites, likes, saves, or bookmarks
complaintsCountNoTotal number of complaints (spam reports, dislikes)
impressionsCountNoTotal number of times content was displayed
uniqueViewsCountNoTotal number of unique users who saw the content
salesCurrencyCodeNoCurrency code for sales amount
uniqueClicksCountNoTotal number of unique clicks
unsubscribesCountNoTotal number of unsubscribes/unfollows
firstTimeCustomersNoNumber of first-time customers who placed orders
returningCustomersNoNumber of returning customers who placed orders
adSpendCurrencyCodeNoThe currency code for ad spend (e.g., 'USD', 'CAD', 'EUR')
marketingActivityIdNoThe ID of the marketing activity for activity-level engagements (e.g., 'gid://shopify/MarketingActivity/123456'). Either this or remoteId should be set for activity-level, not both.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the required write_marketing_events scope, which is a useful auth prerequisite, and the act of creation implies mutation. However, it does not explain idempotency, duplicate handling, response behavior, or other side effects beyond the scope requirement.

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, comprising three short sentences that front-load the purpose, add a brief list of tracked metrics, and state the required scope. Every sentence contributes useful information without redundancy or fluff.

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?

Despite being a complex tool with 26 parameters, no output schema, and no annotations, the description is incomplete. It does not explain how to choose between activity-level and channel-level engagements, the mutual exclusion of remoteId and marketingActivityId, the preference for non-cumulative data, or what a successful creation returns. The description provides insufficient high-level context for an agent to use the tool correctly beyond basic purpose.

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%, so the baseline is 3. The description mentions tracked interaction types that map to some parameters (e.g., clicks, impressions, sales), but it does not add syntax, format, or relationship details beyond what the schema already provides. The mutually exclusive remoteId/marketingActivityId and channelHandle are documented in the schema, not the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a marketing engagement for a marketing activity or channel, and lists the tracked interaction types (clicks, impressions, conversions, sales, orders). This distinguishes it from related marketing tools like create_marketing_event by focusing on engagement metrics and specifying the resource and scope.

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?

The description implies when to use the tool by mentioning it is for marketing activities or channels, but it does not explicitly address alternatives like create_marketing_event or provide exclusions. It also notes the required scope, giving some context, but lacks clear when-to-use versus alternative guidance.

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/UVU-Store/shopify-graphql-mcp'

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