Go Shift

Snapchat performance by product

snapchat_product_performance

Read-only

Which catalog products Snapchat showed in catalog (dynamic) ads: impressions, swipes, swipe rate and spend per product ID, for the account or one campaign. Snapchat returns the top 50 products of each campaign by impressions, not the whole catalog, and gives no purchases or revenue per product, so judge sales at ad or ad squad level. Product IDs are the catalog's IDs. Read-only. Default: last 7 days (7 days at most).

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": "snapchat_product_performance"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Rows to show. Default 25.
`folder`	No	Client folder name.
`account`	No	Snapchat ad account name or ID. Optional when only one is enabled.
`campaign`	No	Limit to one catalog campaign (name or ID).
`end_date`	No	YYYY-MM-DD.
`language`	No	Language of the card: the language the user is writing in.
`date_range`	No	Preset period. Default LAST_7_DAYS.
`start_date`	No	YYYY-MM-DD (with end_date).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), yet the description adds substantive behavior the annotations cannot: the data is truncated to the top 50 products per campaign rather than the whole catalog, purchases and revenue are unavailable, and the date window defaults to 7 days and cannot exceed 7 days. These are exactly the constraints an agent needs before trusting results.

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?

The key scoping and metric information is front-loaded, and each clause (top-50 cap, no revenue, date cap) carries decision-relevant content. 'Read-only.' is redundant with readOnlyHint=true, a minor waste that keeps it from a 5.

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?

With 8 optional parameters and no output schema, the description does a good job naming the returned dimensions and the data limitations, so an agent knows what it will get back. It says little about how folder/account resolution interacts when multiple accounts are enabled, but the schema descriptions cover those fields adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: product IDs are the catalog's IDs, and the maximum 7-day window constrains date_range/start_date/end_date in a way the schema does not (the schema merely says 'Default LAST_7_DAYS'). The top-50 note also implicitly bounds what 'limit' rows will contain.

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 opens with a specific verb+resource: which catalog products Snapchat showed in catalog (dynamic) ads, and enumerates the exact metrics (impressions, swipes, swipe rate, spend per product ID). Scope is stated as 'for the account or one campaign', which distinguishes it from the campaign/ad-squad level siblings such as snapchat_performance.

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

Usage Guidelines4/5

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

It gives a clear when-to-use context (catalog/dynamic ads, product-level view) and an explicit when-not/redirect: 'gives no purchases or revenue per product, so judge sales at ad or ad squad level', pointing the agent to other tools for sales analysis. It does not name a specific alternative tool, keeping it short of a 5.

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

All Go Shift tools Inspect

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

Need Help?