Skip to main content
Glama
Sign In

AdsAgent — Meta Ads MCP

by md.adsagent
OverviewDiscussionsAdmin

support_report_error

Save a report for your owned support_ref in the private AdsAgent support queue. Accepts bounded error classifications, no external recipient. Does not retry or change an advertising operation

Input Schema

NameRequiredDescriptionDefault
requestYes

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. Changed9 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • addedInput schema / properties / request / properties
      Added value: +{
+  "client": {
+    "additionalProperties": false,
+    "properties": {
+      "guide_version": {
+        "maxLength": 16,
+        "minLength": 12,
+        "pattern": "^\\d{4}-\\d{2}-\\d{2}\\.\\d{1,4}$",
+        "type": "string"
+      },
+      "name": {
+        "enum": [
+          "chatgpt",
+          "claude",
+          "codex",
+          "cursor",
+          "other"
+        ],
+        "type": "string"
+      },
+      "skill_pack_version": {
+        "maxLength": 80,
+        "minLength": 1,
+        "pattern": "^(?:[vV]?\\d+(?:\\.\\d+){0,3}(?:[-+][A-Za-z0-9.-]{1,32})?|git:[0-9a-fA-F]{7,40})$",
+        "type": "string"
+      },
+      "version": {
+        "maxLength": 80,
+        "minLength": 1,
+        "pattern": "^(?:[vV]?\\d+(?:\\.\\d+){0,3}(?:[-+][A-Za-z0-9.-]{1,32})?|git:[0-9a-fA-F]{7,40})$",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "idempotency_key": {
+    "maxLength": 128,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9][A-Za-z0-9._:/+-]{0,127}$",
+    "type": "string"
+  },
+  "locale": {
+    "maxLength": 35,
+    "minLength": 2,
+    "pattern": "^[A-Za-z]{2,8}(?:-[A-Za-z0-9]{1,8}){0,3}$",
+    "type": "string"
+  },
+  "observation_code": {
+    "enum": [
+      "agent_stopped_fail_closed",
+      "contract_failed",
+      "dependency_failed",
+      "partial_result_unusable",
+      "suspected_regression",
+      "unexpected_server_error",
+      "verification_inconsistent"
+    ],
+    "type": "string"
+  },
+  "submission_mode": {
+    "enum": [
+      "automatic",
+      "manual"
+    ],
+    "type": "string"
+  },
+  "support_ref": {
+    "maxLength": 27,
+    "minLength": 27,
+    "pattern": "^merr_[A-Za-z0-9_-]{22}$",
+    "type": "string"
+  },
+  "task_stage": {
+    "enum": [
+      "setup",
+      "discovery",
+      "read",
+      "prepare",
+      "approval",
+      "confirm",
+      "verification",
+      "reconciliation",
+      "export",
+      "upload"
+    ],
+    "type": "string"
+  },
+  "user_impact": {
+    "enum": [
+      "none",
+      "degraded",
+      "partial_result",
+      "operation_blocked",
+      "write_outcome_uncertain"
+    ],
+    "type": "string"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "support_ref",
+  "idempotency_key",
+  "submission_mode",
+  "task_stage",
+  "user_impact"
+]
    • addedOutput schema / else / then / properties / category
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / expected
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / else / then / properties / failure_kind
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / responsibility_hint
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / route
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / else / then / properties / user_visible
      Added value: +{
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / connection_context
      Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations: annotations only say non-destructive/closed-world, while the description adds that the report lands in a private queue, has no external recipient, and neither retries nor mutates an advertising operation. It does not cover idempotency behavior or what happens on a repeat submission, which would have made it a 5.

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 short sentences, front-loaded with the action and destination, followed by the scope constraint and the no-side-effect guarantee. No filler and nothing repeated from 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?

For a closed-world, non-destructive write with an output schema, the description covers destination, privacy, and side-effect boundaries adequately. The main residual gap is the idempotency/submission_mode contract, which an agent would need from the schema alone.

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% and the single 'request' parameter hides ten nested fields, yet the description only illuminates support_ref ownership and the 'bounded error classifications' (observation_code). Nothing explains idempotency_key semantics, submission_mode (automatic vs manual), task_stage, or user_impact, so compensation for the coverage gap is partial.

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?

States a concrete verb+resource: saving an error report keyed to an owned support_ref into a private AdsAgent support queue. That clearly separates it from sibling support_get_report_status (read counterpart), though the sibling is not named explicitly.

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?

Usage is implied rather than stated: the agent must already hold an owned support_ref and a bounded error classification. There is no explicit 'use this when...' or 'do not use this for...', and no mention of when to prefer support_get_report_status instead.

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