meta-ads-mcp

meta_ads_configure

Configure Meta Ads API connection by storing your ad account ID, app ID, and app secret to enable authenticated access to campaign management and insights.

Instructions

Meta Ads APIの接続設定を保存します

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": {
      "ad_account_id": "<ad_account_id>",
      "app_id": "<app_id>",
      "app_secret": "<app_secret>"
    },
    "name": "meta_ads_configure"
  }
}

Input Schema

Name	Required	Description
`ad_account_id`	Yes	広告アカウントID（act_XXXXX形式）
`app_id`	Yes	MetaアプリID
`app_secret`	Yes	Metaアプリシークレット

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It indicates a write operation ('save') but does not detail side effects, idempotency, overwrite behavior, or authentication requirements. The agent cannot anticipate what happens if settings already exist.

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 description is a single concise sentence that conveys the core purpose without filler. However, it is extremely brief and could be expanded without sacrificing conciseness.

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

Completeness2/5

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

Given no output schema and the sensitivity of a configuration tool, the description lacks important context: what happens after saving (success/failure), whether previous settings are overwritten, and any required setup steps. The agent may not know if the tool is intended for initial setup or updates.

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 the schema already describes all three parameters adequately. The description adds no additional parameter semantics beyond the schema, earning the baseline score of 3.

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 'Save the connection settings for the Meta Ads API' uses a specific verb (save) and clearly identifies the resource (connection settings). It distinguishes from sibling tools like meta_ads_api_get or meta_ads_authenticate, which are API calls or authentication flows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives (e.g., meta_ads_authenticate or meta_ads_save_token). It does not mention prerequisites, setup order, or context for usage.

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

Deploy Server