Skip to main content
Glama
Mike25app

scaleforge-mcp-meta-ads

list_campaigns

List campaigns from a Meta Ads account, returning id, name, status, objective, daily and lifetime budgets, and bid strategy. Filter by effective status and paginate with limit and cursor.

Instructions

List campaigns in an ad account. Returns id, name, status, objective, daily_budget, lifetime_budget, bid_strategy, created_time. Paginated via limit + after cursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_account_idYesAd Account ID — accepts 'act_123456' or just '123456'
limitNoDefault 100
afterNoPagination cursor
effective_statusNoFilter by effective_status (e.g. ['ACTIVE','PAUSED'])
fieldsNoOverride default field list

Implementation Reference

  • The handler function for list_campaigns. It accepts args (ad_account_id, limit, after, effective_status, fields) and makes a GET request to the Meta Graph API endpoint for the ad account's campaigns, passing query params with a default field set and pagination support.
    handler: async (args) =>
      metaGet(`/${toAdAccountPath(String(args.ad_account_id))}/campaigns`, {
        fields: args.fields ?? DEFAULT_CAMPAIGN_FIELDS,
        limit: args.limit ?? 100,
        after: args.after,
        effective_status: args.effective_status,
      }),
Behavior4/5

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

Discloses pagination and return fields. No annotations provided, so description carries burden; but doesn't explicitly state it's read-only or mention side effects, though implicit.

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?

Two concise sentences, front-loaded with purpose and return fields, then pagination detail. No verbose or redundant content.

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?

Compensates for lack of output schema by listing return fields. Mentions pagination. Could add ordering, error info, but sufficient for a list tool.

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

Parameters4/5

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

Schema coverage is 100%, but description adds value by listing return fields and confirming pagination cursor usage, which are not fully in schema descriptions.

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?

Clearly states verb 'list' and resource 'campaigns in an ad account', and lists specific return fields, differentiating from siblings like get_campaign or batch operations.

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?

Implies use for listing campaigns but lacks explicit guidance on when to use vs alternatives (e.g., get_campaign for single, search tools). No exclusions noted.

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/Mike25app/scaleforge-mcp-meta-ads'

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