Skip to main content
Glama
Sign In
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

snap_creative_compare

Read-only

Compare ads in a campaign or ad squad by spend, purchases, ROAS, cost per purchase, headline, and call to action; classify each against the median as winner, normal, lagging, or too early.

Instructions

Which ads win? (read-only) Compares the ads of a campaign or ad squad: spend, purchases, ROAS, cost per purchase, headline and call to action, with WINNER / NORMAL / LAGGING / TOO_EARLY against the median, and results grouped by call to action. Ads with less than min_spend are not judged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entity": "<entity>",
      "id": "<id>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "snap_creative_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo
entityYes
end_timeYes
min_spendNo
start_timeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so '(read-only)' earns little. The description does add real behavioral context beyond the annotations: grading is relative to the median, results are grouped by call to action, and ads under min_spend are excluded from judgement.

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?

Three sentences, front-loaded with the value proposition, then scope, then output semantics and the one important caveat. No filler and no repetition of the title.

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 no output schema and no annotation detail, the description still describes the returned metrics and grade categories well. The remaining gap is operational detail for the required inputs (entity scoping, time range format), which an agent must infer from the schema.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, so the description must carry the load. It only clarifies min_spend's effect (ads below it are not judged); entity, id, start_time, end_time and limit are left entirely to the bare schema.

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?

States a specific verb and resource ('Compares the ads of a campaign or ad squad') and enumerates the exact metrics and grading labels returned. An agent can tell this is the creative-level comparison tool rather than a report/clone/fatigue tool.

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 opening question 'Which ads win?' implies the analytical use case, and the min_spend exclusion hints at data-quality caveats. But there is no explicit when-to-use vs alternatives (e.g. report-level comparison or fatigue analysis) and no stated prerequisites.

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

Deploy Server

Other Tools