Snapchat Ads MCP Server

Overview Schema Source Related Servers Discussions Admin

snapchat get entity

snapchat_get_entity

Read-onlyIdempotent

Retrieves a specific Snapchat Ads campaign, ad squad, ad, creative, media, segment, creative element, interaction zone, or lead form from a verified ad account so you can inspect its details.

Instructions

Read a campaign, ad squad, ad, creative, media, segment, creative element, interaction zone or lead form with verified account ownership.

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": {
      "adAccountId": "<adAccountId>",
      "kind": "<kind>",
      "entityId": "<entityId>"
    },
    "name": "snapchat_get_entity"
  }
}

Input Schema

Name	Required	Description
`kind`	Yes	Entity type to read.
`entityId`	Yes	Entity UUID, or the numeric ID of an audience segment.
`adAccountId`	Yes	Snapchat ad account UUID listed in SNAPCHAT_ADS_ACCOUNT_IDS; never an organization ID.

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.0.1Oct 26, 2026

addedInput schema / properties / adAccountId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

changedInput schema / properties / entityId / anyOf

Previous value: -[
-  {
-    "description": "Native Snapchat entity UUID.",
-    "format": "uuid",
-    "type": "string"
-  },
-  {
-    "pattern": "^\\d{1,30}$",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "description": "Native Snapchat entity UUID.",
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+    "type": "string"
+  },
+  {
+    "pattern": "^\\d{1,30}$",
+    "type": "string"
+  }
+]

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv1.0.0Oct 23, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuinely new behavioral context with 'verified account ownership', telling the agent that a cross-account or unauthorized entity will fail rather than return data. It does not describe not-found or error semantics, but the addition is meaningful.

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?

One sentence, front-loaded with the verb, and no filler. It loses a point only because the entity enumeration largely duplicates the kind enum already in the schema.

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 an output schema present and annotations covering safety, the description needs only to state the operation and access requirement, which it does. The main residual gap is that entity-type-specific nuances (e.g., that lead forms or segments may need different identifiers) are left entirely to 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?

Schema description coverage is 100%, and the schema itself documents the kind enum, the dual-format entityId (UUID or numeric audience-segment ID), and the adAccountId constraint. The description restates the entity list but adds nothing on format or edge cases, so the baseline 3 applies.

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 verb 'Read' plus an explicit enumeration of entity types ('campaign, ad squad, ad, creative, media, segment...') makes clear this is a single-entity fetch keyed by kind. It is distinguishable from the sibling list tools (snapchat_get_campaigns, snapchat_get_ads, etc.) only by the singular phrasing, not by any explicit contrast.

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?

There is no statement of when to use this generic getter versus the type-specific siblings, and no mention of prerequisites such as when an entityId is known. The only usage signal is the implicit singular/plural distinction, which the agent must infer.

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