Skip to main content
Glama

create_feed

Create a product feed for a catalog by providing catalog ID, feed name, schedule, and file URL.

Instructions

Create a new product feed for a catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
catalog_idYesProduct catalog ID
nameYesFeed name
scheduleNoJSON string for feed schedule configuration
file_urlNoURL of the feed file

Implementation Reference

  • The create_feed tool handler - registered via server.tool(), accepts catalog_id, name, schedule (optional JSON string), and file_url (optional). Makes a POST to /{catalog_id}/product_feeds via the AdsClient.
    // ─── create_feed ───────────────────────────────────────────
    server.tool(
      "create_feed",
      "Create a new product feed for a catalog.",
      {
        catalog_id: z.string().describe("Product catalog ID"),
        name: z.string().describe("Feed name"),
        schedule: z.string().optional().describe("JSON string for feed schedule configuration"),
        file_url: z.string().optional().describe("URL of the feed file"),
      },
      async ({ catalog_id, ...params }) => {
        try {
          const { data, rateLimit } = await client.post(`/${catalog_id}/product_feeds`, { ...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 for create_feed input: catalog_id (string), name (string), schedule (optional string), file_url (optional string).
    {
      catalog_id: z.string().describe("Product catalog ID"),
      name: z.string().describe("Feed name"),
      schedule: z.string().optional().describe("JSON string for feed schedule configuration"),
      file_url: z.string().optional().describe("URL of the feed file"),
    },
  • src/tools/feeds.ts:5-6 (registration)
    The registerFeedTools function that registers all feed tools (including create_feed) on the MCP server.
    export function registerFeedTools(server: McpServer, client: AdsClient): void {
      // ─── list_feeds ────────────────────────────────────────────
  • src/index.ts:72-72 (registration)
    Where registerFeedTools is called to register feed tools (including create_feed) on the MCP server.
    registerFeedTools(server, client);
  • The AdsClient.post() method used by the create_feed handler to make the HTTP 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?

With no annotations provided, the description should disclose behavioral traits. It only states the action without detailing side effects, permissions, rate limits, or success/failure behavior. This is insufficient for a creation tool.

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 (8 words) with no wasted text. However, it could include more useful context without significant bloat, so it's not a perfect 5.

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 4 parameters (2 required) and no output schema, the description is too minimal. It does not mention that 'catalog_id' and 'name' are required, nor does it clarify what the tool returns (e.g., feed ID). Considerable context is missing for a creation tool.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema. It does not explain the 'schedule' JSON format or 'file_url' requirements, but the schema already provides descriptions for all parameters.

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 ('product feed'), and the scope ('for a catalog'). It distinguishes from siblings like 'upload_feed' and 'list_feeds' by specifying creation of a new feed, not uploading or listing.

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?

No guidance on when to use this tool versus alternatives like 'upload_feed' or 'list_feeds'. The description does not mention prerequisites, context, or when not to use it.

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