Skip to main content
Glama
Ads MCP for Snapchat

Ads MCP for Snapchat

by Usame794

snap_check_landing_pages

Read-only

Checks landing pages used by active Snapchat ads to confirm each link opens over HTTPS, follows redirects, and flags broken, slow, unreachable, cross-site, or missing-required-parameter links.

Instructions

Check that the web pages your ACTIVE ads send people to actually open (read-only; changes nothing in Snap). Each distinct link is opened once from this computer, over https only and never to private addresses; redirects are followed and checked. Flags broken (404), server errors, slow, unreachable and non-https links, and links that end up on another site. Optional required_params (e.g. ["utm_source"]) flags links that lack them. It cannot see 'out of stock' text inside a page that opens.

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

Input Schema

NameRequiredDescriptionDefault
max_linksNo
required_paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses substantial operational behavior: each distinct link is fetched once from this machine, https only, no private addresses, redirects followed and evaluated. It enumerates the failure classes flagged (404, server errors, slow, unreachable, non-https, cross-site redirects) and explicitly states a limitation — it cannot detect 'out of stock' text inside a page. This is unusually complete disclosure for a read-only tool.

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 definition is front-loaded with the core purpose, then layers behavior, failure modes, parameter semantics, and a caveat. Nearly every clause carries information, though the long compound sentence with parentheticals is dense and could be split for easier scanning.

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?

For a two-parameter, no-output-schema read-only tool, the description covers purpose, safety profile, network behavior, failure classification, and a known limitation. The main remaining gap is the undocumented max_links parameter and any indication of how results are summarized or paginated.

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 0%, so the description must carry parameter meaning. It explains required_params well, including an example value and the resulting flagging behavior, but max_links (the default-100, max-300 batch cap) is never mentioned, leaving one of two parameters semantically undocumented.

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 names a specific verb ('Check'), a specific resource (web pages that ACTIVE ads send people to), and constrains scope to active ads only. This is clearly distinguishable from sibling checks like snap_health_check or snap_catalog_feed_status, which target account or feed state rather than outbound ad destinations.

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?

The implicit use case is clear: validate that landing pages your live ads point to are reachable and correct. It also states the scope restriction to ACTIVE ads and hints at the required_params validation use case. However, it never states when not to use it or names an alternative tool for related diagnostics.

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