Skip to main content
Glama
Sign In

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

products_list

Read-only

List products and funnel/MMP event sources

Input Schema

NameRequiredDescriptionDefault
viewNofull
limitNo
cursorNo
channel_pidNo

Output Schema

NameRequiredDescriptionDefault
messageNo
retryableNo
support_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / connection_context
      Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
+  "default": "full",
+  "enum": [
+    "full",
+    "refs"
+  ],
+  "type": "string"
+}
  3. Changed6 schema fields changed
    • addedOutput schema / then / properties / category
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / expected
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / then / properties / failure_kind
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / responsibility_hint
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / route
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / then / properties / user_visible
      Added value: +{
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  5. Changed1 schema field changed
    • addedOutput schema / else / properties / meta / properties / metric_completeness
      Added value: +{
+  "additionalProperties": {
+    "properties": {
+      "complete": {
+        "type": "boolean"
+      },
+      "excluded_rows": {
+        "type": "integer"
+      },
+      "reason": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "object"
+}
  6. Changed1 schema field changed
    • addedOutput schema / else / properties / workspace_ref
      Added value: +{
+  "description": "Opaque workspace comparison hint; not an authorization credential.",
+  "pattern": "^workspace_[0-9a-f]{32}$",
+  "type": "string"
+}
  7. Changed1 schema field changed
    • addedOutput schema / else / properties / meta / properties / data_freshness / properties / last_pull_scope
      Added value: +{
+  "const": "workspace"
+}
  8. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description only adds that the listing spans products and funnel/MMP event sources, but says nothing about pagination behavior or how 'view' changes the response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single short sentence is front-loaded and free of bloat. However, it is under-specified for a tool with four parameters and a view-mode enum, so its brevity comes at the cost of useful detail.

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

Completeness2/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 annotations cover safety. But with 0% schema coverage on four parameters, the definition is not complete enough for an agent to call the tool correctly, particularly regarding view mode and pagination.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters, yet the description provides no explanation of any parameter. The critical 'view' enum (full vs. refs), the limit maximum, the cursor pagination token, and the channel_pid filter are all left entirely undocumented.

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?

States the verb 'List' and two resources ('products' and 'funnel/MMP event sources'), so the basic purpose is recoverable. However, it doesn't differentiate itself from closely related siblings such as products_get_funnel_candidates, products_get_funnel_values, or mmp_get_state, and the combined 'funnel/MMP event sources' phrasing is ambiguous.

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 guidance on when to use this tool versus the many product and MMP siblings, and no mention of prerequisites or exclusions. The agent must infer usage from the name alone.

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

All AdsAgent — Meta Ads MCP toolsInspect
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