AdsAgent — Meta Ads MCP

accounts_get_account_detail

Read-only

Read live Meta account details; app bindings are cached, no BM links. BM topology: assets_lookup_business_links

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ad_account_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No
`retryable`	No
`support_ref`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 24, 2026

addedOutput schema / else / properties / availability

Added value: +{
+  "additionalProperties": {
+    "enum": [
+      "available",
+      "partial",
+      "unavailable"
+    ]
+  },
+  "propertyNames": {
+    "enum": [
+      "pages",
+      "pixels",
+      "account",
+      "apps"
+    ]
+  },
+  "type": "object"
+}

addedOutput schema / else / properties / complete
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / else / properties / status

Added value: +{
+  "enum": [
+    "complete",
+    "partial"
+  ]
+}

addedOutput schema / else / properties / warnings

Added value: +{
+  "items": {
+    "properties": {
+      "action_url": {
+        "type": "string"
+      },
+      "category": {
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "retryable": {
+        "type": "boolean"
+      },
+      "section": {
+        "enum": [
+          "pages",
+          "pixels",
+          "account",
+          "apps"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

First observedSep 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag this as read-only and non-destructive; the description adds operational nuance: data is live from Meta but app bindings are cached, and BM links are excluded. This helps set expectations about staleness and scope without contradicting annotations.

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 concise clauses with no filler; 'Read live Meta account details' is front-loaded and every added phrase ('app bindings are cached', 'no BM links', sibling pointer) contributes new information.

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 single-parameter read-only tool with an output schema and safety annotations, the description covers the central purpose, caching caveat, and the key sibling for BM topology. Slightly more explicit guidance on when to choose this over account_get_profile would make it fully complete.

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?

The schema description coverage is 0% and the description provides no guidance on the ad_account_id value's origin or format. The one parameter's name is self-explanatory, but the description does not compensate for the schema coverage gap.

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 specific action and resource: 'Read live Meta account details.' The caveat 'app bindings are cached, no BM links' and pointer to assets_lookup_business_links clarify scope against BM-topology tools, though it does not explicitly distinguish from the sibling account_get_profile.

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?

Supplies context that this tool exposes account details and explicitly routes 'BM topology' to assets_lookup_business_links, which acts as a when-not alternative. It does not spell out other competing cases such as account_get_profile or list tools.

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 tools Inspect

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

Need Help?