Skip to main content
Glama
Sign In
Meta Ads MCP Server

Meta Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List hosted tools

list_hosted_tools
Read-onlyIdempotent

Lists hosted Meta Ads tools with one-line summaries, helping agents understand available ad account actions like campaign creation and performance reporting.

Instructions

List the tools of the hosted Meta Ads MCP server by AdKit (https://mcp.adkit.so/meta-ads), with one line on what each tool does. Use this to explain what an agent can do with ad accounts after connecting, such as creating campaigns, pulling performance or uploading media. Returns a Markdown table. It does not call those tools; they only run on the hosted server.

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": "list_hosted_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds meaningful behavior beyond that: the return format (a Markdown table), the one-line-per-tool granularity, and the important caveat that this tool only enumerates the hosted tools and does not invoke them.

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?

Four short sentences, each carrying distinct information: what is listed, when to use it, what it returns, and what it does not do. The purpose is front-loaded and nothing is repeated.

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 zero-parameter tool with no output schema, the description covers everything an agent needs: the source server, the output format, the intended use case, and the caveat that the listed tools run elsewhere. Annotations handle the safety profile, so no gaps remain.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste space inventing parameter details, which is correct for an argument-free listing call.

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?

The description gives a specific verb and resource: listing the tools of the hosted Meta Ads MCP server by AdKit, with one line per tool. The final sentence clearly separates this listing operation from the hosted tools themselves ("It does not call those tools"). It does not, however, explicitly differentiate itself from the sibling list_ad_platforms, leaving a small risk of confusion between the two listing tools.

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?

"Use this to explain what an agent can do with ad accounts after connecting" gives a clear contextual trigger, plus concrete examples of the capabilities to be described (creating campaigns, pulling performance, uploading media). There are no explicit exclusions or named alternatives, so it falls short of a 5.

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