Skip to main content
Glama

Ads Uploader: Meta Ads MCP

Read Account Details

ads_get_account
Read-onlyIdempotent

Read an owned Meta ad account’s status, currency, timezone, spend and funding display. Money includes major amounts and raw minor-unit strings. Includes the read-only metaEdits enabled setting and approval rule, plus permissions (visible, read, launch and edit as off, approval or allowed, approvalRule) from the Account Permissions page; CLI/MCP cannot change them. A 429 carries Retry-After. ROW_QUOTA_EXCEEDED carries the time the quota resets (meta.quota.resetsAt).

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": {
      "accountId": "<accountId>"
    },
    "name": "ads_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass the read cache.
accountIdYesAd account ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, yet the description adds real value beyond them: money returned in both major amounts and raw minor-unit strings, the read-only metaEdits setting, and that permission fields cannot be modified via CLI/MCP. It also discloses failure behavior precisely, including a 429 with Retry-After and ROW_QUOTA_EXCEEDED carrying meta.quota.resetsAt.

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?

The purpose is front-loaded in the first clause, and the following sentences map to distinct concerns: return shape, read-only settings, permissions, and error semantics. It is dense and enumerates several return fields inline, but with no output schema each of those details earns its place; only minor tightening is possible.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing the return payload, and it does so concretely (status, currency, timezone, spend/funding display, money units, permission fields). Error semantics for 429 and quota exhaustion are also covered, leaving nothing an agent needs to call this correctly.

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 (accountId and fresh) are already documented, including the cache-bypass meaning of fresh. The description adds no further syntax or format detail about parameters, so the baseline of 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?

States a specific verb and resource: 'Read an owned Meta ad account's status, currency, timezone, spend and funding display.' The singular 'an owned ... account' plus the required accountId distinguishes it from ads_list_accounts, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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 context is implied by the field list and the required account ID, and 'CLI/MCP cannot change them' signals a read-only boundary. However, there is no explicit when-to-use statement or comparison to alternatives such as ads_list_accounts for enumeration.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.