Skip to main content
Glama

create_block_list

Create a publisher block list to exclude specific publishers from your ad placements in Facebook and Instagram campaigns.

Instructions

Create a new publisher block list for the ad account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the block list

Implementation Reference

  • The handler function for the create_block_list tool. It accepts a 'name' parameter and POSTs to the Meta Ads API endpoint /publisher_block_lists to create a new publisher block list.
    server.tool(
      "create_block_list",
      "Create a new publisher block list for the ad account.",
      {
        name: z.string().describe("Name for the block list"),
      },
      async ({ name }) => {
        try {
          const params: Record<string, unknown> = { name };
          const { data, rateLimit } = await client.post(`${client.accountPath}/publisher_block_lists`, params);
          return { content: [{ type: "text" as const, text: JSON.stringify({ ...data as object, _rateLimit: rateLimit }, null, 2) }] };
        } catch (error) {
          return { content: [{ type: "text" as const, text: `Failed: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
        }
      }
    );
  • Zod schema defining the input for create_block_list: a required string field 'name'.
    {
      name: z.string().describe("Name for the block list"),
    },
  • Registration function that registers all brand safety tools (including create_block_list) on the MCP server.
    export function registerBrandSafetyTools(server: McpServer, client: AdsClient): void {
  • src/index.ts:86-86 (registration)
    The call site where registerBrandSafetyTools is invoked in the main server setup.
    registerBrandSafetyTools(server, client);
  • The AdsClient.post method used by the handler to send the POST request to the Meta Ads API.
    async post(
      path: string,
      params?: Record<string, unknown>
    ): Promise<ClientResponse> {
      return this.request("POST", path, params);
    }
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It indicates a write operation ('Create') but lacks details on idempotency, uniqueness constraints, side effects, permissions, or return values.

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 a single 11-word sentence that is concise and front-loaded with the action. Every word is necessary.

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

Completeness3/5

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

For a simple creation tool with one parameter and no output schema, the description is adequate but could be more complete by noting return behavior (e.g., returns the list ID).

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?

The input schema already defines the 'name' parameter with a description. The tool description adds no additional meaning beyond what the schema provides, so 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?

The description clearly states the action ('Create'), the resource ('publisher block list'), and scope ('for the ad account'). It distinguishes from sibling tools like 'add_to_block_list' and 'delete_block_list'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives like 'add_to_block_list' or prerequisites. Usage is implied but not directly addressed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikusnuz/meta-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server