Skip to main content
Glama

Honeyfield Marketing MCP

Meta Ads: List campaigns

meta_list_campaigns
Read-only

Meta-Kampagnen des Ad-Accounts auflisten (Status, Ziel, Budgets in EUR); issues zeigt Delivery-Probleme aus issues_info, wenn vorhanden. Felder je Kampagne: status, effective_status, objective, daily_budget_eur/ lifetime_budget_eur (CBO = eines davon gesetzt), bid_strategy (nur bei CBO, sonst null — dann liegt sie am Adset), spend_cap_eur (Ausgabenlimit der Kampagne; null = kein Limit), budget_remaining_eur (nur bei CBO; null ohne Kampagnenbudget — dann liegt das Budget an den Adsets), special_ad_categories (Liste, [] = keine), buying_type (AUCTION/RESERVED), start_time, stop_time, updated_time, issues — zum Zurücklesen nach meta_create_campaign/ meta_update_campaign. start_time/stop_time leitet Meta aus den Adsets ab (null ohne Adset-Enddatum) — das Enddatum wird je Adset gesetzt (meta_update_adset end_time). limit: max. Anzahl (Default 50). Wird abgeschnitten (Meta meldet weitere Seiten), kommt statt der Liste ein Objekt mit result und warning zurück — dann limit erhöhen. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "meta_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The critical behavioral trait is disclosed: when Meta reports more pages, the tool returns an object with result and warning instead of a list, and the agent should raise limit. It also explains the null semantics per field (bid_strategy null means set at adset level, budget_remaining null means no campaign budget), which is real context beyond readOnlyHint/openWorldHint. Nothing contradicts the read-only annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and pagination warning are front-loaded, but the bulk of the text is a field-by-field enumeration of return values that an output schema already covers. It is long for a two-parameter list tool and the redundant field list dilutes the truly important sentences.

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?

Everything needed to call it correctly (limit semantics, workspace, pagination failure mode) is present, and the provenance of start_time/stop_time from adsets is a useful caveat. The return-field detail is redundant given the output schema, so it is complete but not efficiently so.

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 description coverage is 0%, so the description carries the full burden and does so: limit is max count with default 50 and a defined truncation consequence; workspace is the customer workspace slug and is optional when only one workspace exists.

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 ('Meta-Kampagnen des Ad-Accounts auflisten') plus the key dimensions returned, so it is clearly distinguishable from meta_list_adsets/meta_list_ads. It does not name those siblings explicitly, so it stops just short of a 5.

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?

Gives an explicit read-back-after-write context ('zum Zurücklesen nach meta_create_campaign/meta_update_campaign'), which tells the agent when to reach for it. No exclusion guidance (e.g. when to use meta_campaign_performance instead of this list) is provided.

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.

Resources