Skip to main content
Glama
Sign In
Meta Ads MCP Server

Meta Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get setup guide

get_setup_guide
Read-onlyIdempotent

Returns step-by-step instructions to connect an AI app to the hosted Meta Ads MCP server, including the exact menu path, command, or config snippet needed.

Instructions

Get the step-by-step instructions to connect one AI app to the hosted Meta Ads MCP server by AdKit at https://mcp.adkit.so/meta-ads. Use this when the user asks how to install, add or connect AdKit in a specific app. Returns Markdown with the exact menu path, command or config snippet. For what the hosted server can do once connected, use list_hosted_tools instead.

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": {
      "app": "<app>"
    },
    "name": "get_setup_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe AI app to connect, exactly as listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the output shape (Markdown containing the exact menu path, command, or config snippet) and the one-app-at-a-time scope. It stops short of noting e.g. that guides are static/versioned or that the returned steps may differ per app, which would push this to a 5.

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?

Three sentences, front-loaded with the purpose, then the trigger, then the return format, then the sibling redirect. Every sentence carries distinct information and there is no redundant restatement of the tool name.

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

Completeness5/5

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

For a one-enum-parameter read-only lookup with no output schema, the description supplies purpose, trigger, and the shape of the Markdown return value. Nothing an agent needs in order to call it correctly, or to decide against calling it, is missing.

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% and the single parameter is a six-value enum already documented as "The AI app to connect, exactly as listed." The description's only addition is the phrase "in a specific app," which reinforces the one-app constraint but adds no syntax or selection guidance beyond the schema. Baseline 3 is appropriate.

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 ("Get the step-by-step instructions to connect one AI app to the hosted Meta Ads MCP server") and names the concrete endpoint. It also explicitly contrasts itself with the sibling list_hosted_tools, so an agent can distinguish discovery-of-capabilities from discovery-of-setup-steps.

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

Usage Guidelines5/5

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

Gives an explicit triggering condition ("Use this when the user asks how to install, add or connect AdKit in a specific app") and an explicit alternative for the adjacent need ("For what the hosted server can do once connected, use list_hosted_tools instead"). Both when-to-use and when-to-use-something-else are covered.

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

Deploy Server

Other Tools