Meta Ads by Get MCP Ads

meta get uploaded video

meta_get_uploaded_video

Read-onlyIdempotent

Verifies video processing and account-library membership for a Meta Ads account, using bounded pagination and title-based lookup when the ID is not found on the first page.

Instructions

Check video processing and membership in the selected account library. If the first page misses the ID, use the video title to narrow the account-scoped lookup. A direct video read alone never proves membership or readiness. Bounded pagination; not_found is not success.

Input Schema

Name	Required	Description	Default
`videoId`	Yes	Exact uploaded video ID returned by Meta in this account.
`adAccountId`	Yes	Owning advertising account ID. Use the exact ID returned by account discovery; do not substitute a campaign or business 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.

Changed2 schema fields changedv2.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

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 observedv2.0.1Sep 23, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond that: lookups are 'bounded pagination', the scope is the account library, and 'not_found is not success' warns that a negative result is not proof of absence. Only the fallback mechanism is left opaque.

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?

Four short sentences, no filler, and the verification intent plus the failure-semantics warning are front-loaded. The only wasted content is the title-based lookup advice, which does not correspond to any input the tool accepts.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers membership/readiness semantics and pagination bound. The gap is the instructed fallback: an agent told to 'use the video title to narrow the account-scoped lookup' has only videoId and adAccountId available, leaving the recovery path unexplained and potentially unexecutable.

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 both parameters are already documented and the baseline is 3. The description reinforces account scoping ('the selected account library', 'account-scoped lookup'), but it also references a 'video title' narrowing path for which no parameter exists, which muddies rather than clarifies parameter usage.

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

Purpose3/5

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

The description frames the tool as a verification step ('Check video processing and membership in the selected account library') rather than plainly stating it fetches an uploaded video record by ID, so the primary action must be inferred. It does distinguish itself from list-oriented siblings like meta_list_ad_videos by emphasizing per-ID membership/readiness checks, but the framing is oblique.

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?

It gives situational cues ('If the first page misses the ID...', 'A direct video read alone never proves membership or readiness') that imply when this verification is needed, which is more than nothing. However, it never names the sibling tools an agent should consider instead (meta_list_ad_videos, meta_get_video_sources), and the advised fallback path is not actionable given the parameters.

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

Deploy Server