Skip to main content
Glama

meta_ads_feeds_create

Create a scheduled product feed to import products into a Meta catalog from a URL, supporting CSV, TSV, RSS, Atom, or JSON formats. Choose hourly, daily, or weekly updates for ongoing bulk sync.

Instructions

Creates a scheduled product feed that imports products into a catalog from a URL. Returns the new feed_id. Mutating, reversible via rollback_apply. Feeds run automatically on the chosen schedule; the first run triggers shortly after creation. For one-off product adds use meta_ads_products_add — feeds are for ongoing bulk sync. Supported feed formats: CSV, TSV, RSS 2.0, Atom 1.0, JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
catalog_idYesCatalog that will consume the feed.
nameYesFeed name shown in Commerce Manager. Should be unique within the catalog.
feed_urlYesHTTPS URL Meta will fetch on each scheduled run. Must be publicly reachable. Meta supports basic auth or signed-URL patterns if configured separately.
scheduleNoHow often Meta re-fetches and re-ingests the feed. Default DAILY. HOURLY is appropriate for fast-moving inventory (fashion flash sales); WEEKLY fits evergreen catalogs.
Behavior4/5

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

Discloses mutation, reversibility, and automatic schedule triggering. No annotations exist, so description carries burden well, though misses auth/rate limits.

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?

Single concise paragraph with key info front-loaded. No unnecessary words.

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?

Explains return value, scheduling, reversibility, and sibling tool. Lacks error handling details but sufficient for typical use.

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% with detailed descriptions. Description adds marginal value (e.g., feed formats) but baseline adequate.

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 it creates a scheduled product feed and returns a feed_id. It distinguishes from sibling tool meta_ads_products_add for one-off adds.

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?

Explicitly advises use for ongoing bulk sync vs meta_ads_products_add for one-off. Also mentions reversibility via rollback_apply.

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/logly/mureo'

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