Skip to main content
Glama
hashcott

Meta Ads MCP Server

by hashcott

Get Meta Ad Account Details

meta_ads_get_ad_account_details
Read-onlyIdempotent

Retrieve detailed information about a Meta ad account, including status, balance, currency, and spend. Use the ad account ID to fetch the details.

Instructions

Get detailed information about a specific Meta ad account.

Args:

  • act_id (string): The ad account ID prefixed with 'act_', e.g., 'act_1234567890'

  • fields (string[]): Optional. Fields to retrieve. If omitted, defaults to: name, business_name, age, account_status, balance, amount_spent, attribution_spec, account_id, business, business_city, brand_safety_content_filter_levels, currency, created_time, id.

Returns: Object with the requested ad account fields. Key fields:

  • id (string): Ad account ID

  • name (string): Account display name

  • account_status (number): Status code (1=ACTIVE, 2=DISABLED, 3=UNSETTLED, etc.)

  • currency (string): Account currency code (e.g., 'USD')

  • balance (string): Current account balance

  • amount_spent (string): Total lifetime spend

Examples:

  • Use when: "Get details for ad account act_123456"

  • Use when: "What is the currency and balance of my ad account?"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
act_idYesAd account ID prefixed with 'act_', e.g., 'act_1234567890'
fieldsNoList of specific fields to retrieve. If omitted, default fields are returned
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral context: it explains the structure of the return object, the meaning of account_status codes (e.g., 1=ACTIVE), and that omitted 'fields' parameter defaults to a list of common fields. No contradictions with 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?

The description is concisely structured with a summary, Args, Returns, and Examples sections. Every sentence serves a purpose. It is not verbose, and the format makes it easy for an agent to parse quickly. No wasted text.

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?

For a simple, read-only tool without an output schema, the description provides complete context: purpose, parameters with format, return object explanation with key fields and status codes, and usage examples. It fully addresses the tool's complexity and leaves no gaps for correct invocation.

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

Parameters5/5

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

Schema coverage is 100%, both parameters have descriptions. The description adds beyond the schema: it specifies the 'act_' prefix for act_id, lists the default fields for the optional 'fields' parameter, and provides the return object structure including key fields and their types. This significantly enhances understanding.

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

Purpose5/5

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

The description clearly states the tool gets detailed information about a specific Meta ad account. It distinguishes from siblings like 'meta_ads_list_ad_accounts' (listing all accounts) and 'meta_ads_get_adaccount_insights' (insights). The verb 'Get' and resource 'detailed information about a specific Meta ad account' are precise.

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?

The description provides two concrete 'Use when' examples, giving context for when to invoke the tool. However, it does not explicitly state when _not_ to use this tool or suggest alternative tools for listing all accounts or retrieving insights. This omission keeps it from a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hashcott/meta-ads-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server