Skip to main content
Glama

Honeyfield Marketing MCP

Meta Ads: List ad accounts

meta_list_ad_accounts
Read-only

Erreichbare Meta-Ad-Accounts der Verbindung auflisten (id, Name, Status, Währung) — um die richtige Account-ID zu finden, die im Workspace einzutragen ist. 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_ad_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds real value beyond that: the result is scoped to accounts reachable via the current connection, the four returned fields, and the conditional behaviour of the workspace parameter ('optional bei nur einem Workspace'). It does not say what happens if several workspaces exist and none is supplied.

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 compact sentences: the primary action and its purpose first, the parameter note second. No filler, no repetition of the title.

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?

With an output schema present, return values need not be spelled out (the field list is a bonus), and the single parameter is addressed. What is missing is only the edge-case behaviour for workspace resolution and a pointer to list_workspaces for discovering the slug.

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 0%, so the description must carry the parameter, and it does: 'workspace' is defined as the customer workspace slug, nullable and optional when only one workspace exists. The main residual gap is the failure/default behaviour when multiple workspaces exist and the parameter is omitted.

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?

States a specific verb and resource ('Erreichbare Meta-Ad-Accounts ... auflisten') and even enumerates the returned fields (id, Name, Status, Währung). It is clearly distinguishable from siblings like meta_account_status (status of one account) or meta_list_campaigns (children of an account), and it names the downstream purpose: finding the account ID to store in the workspace.

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 gives a clear context of use ('um die richtige Account-ID zu finden, die im Workspace einzutragen ist'), which is exactly the discovery step before any meta_* campaign call. It stops short of naming an alternative or stating when not to use it (e.g. when the account ID is already known, or pointing to list_workspaces to obtain the slug).

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