Meta Ads MCP

Overview Schema Source Related Servers Discussions Admin

graph_call

Call any Meta Graph API endpoint directly. Specify HTTP method, endpoint, query parameters, and body to read or modify resources.

Instructions

Call any Graph API endpoint directly.

Args: method: GET, POST, or DELETE. endpoint: Path AFTER the version prefix, e.g. "act_123/campaigns" or "me/adaccounts". Do NOT include "https://graph.facebook.com/v21.0/" — that's added automatically. params: Query string parameters as a dict. data: Body parameters for POST as a dict. confirm: Required True for POST and DELETE.

Examples: - Read your user info: graph_call("GET", "me", {"fields": "id,name"}) - Get adaccount: graph_call("GET", "act_123", {"fields": "name,balance"}) - Pause ad: graph_call("POST", "12345", data={"status":"PAUSED"}, confirm=True)

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": {
      "method": "<method>",
      "endpoint": "<endpoint>"
    },
    "name": "graph_call"
  }
}

Input Schema

Name	Required	Description	Default
`data`	No
`method`	Yes
`params`	No
`confirm`	No
`endpoint`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Without annotations, the description carries the full burden. It discloses several behavioral traits: the version prefix is added automatically, confirm is required for POST and DELETE, and it distinguishes between params (query string) and data (body). It does not mention error handling or rate limits, but the provided details are meaningful and go beyond the schema.

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 well-structured and concise. It opens with a clear one-line purpose, then logically groups parameter explanations, and ends with three concrete examples. Every sentence adds value, and the format is easy to parse.

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?

For a low-level API caller with no output schema, the description provides sufficient invocation detail: methods, endpoint format, parameter types, and confirmation requirement. It lacks explicit mention of return values or pagination, but the standard behavior of a raw API call is implied, and the presence of graph_paginate as a sibling covers that gap somewhat.

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 must compensate. It thoroughly explains every parameter: method (GET/POST/DELETE), endpoint (path after version prefix with a key exclusion), params (query dict), data (body dict), and confirm (required for writes). Examples illustrate usage effectively, fully compensating for the schema silence.

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 states 'Call any Graph API endpoint directly,' which clearly identifies it as a generic, low-level API caller. This distinguishes it from specialized sibling tools like ads_pause_campaign or pages_publish_post, which target specific operations.

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 clearly implies this tool is for direct Graph API calls beyond the specialized high-level tools. It explains the context (call any endpoint) but does not explicitly state 'use specialized tools when available' or list exclusions, so it lacks explicit when-not guidance.

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

Deploy Server