Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_feeds_create

Create a scheduled product feed to import products into a catalog from a public URL, with automated hourly, daily, or weekly sync, returning the new feed_id for ongoing bulk updates.

Instructions

Creates a scheduled product feed that imports products into a catalog from a URL. Returns the new feed_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. 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
nameYesFeed name shown in Commerce Manager. Should be unique within the catalog.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does it well. It discloses that the operation is mutating, not automatically reversible, recommends recording before-state with mureo_state_action_log_append for rollback, and notes that feeds run automatically and start shortly after creation.

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 compact and front-loaded: purpose, return value, mutation caveat, rollback guidance, schedule behavior, sibling alternative, and supported formats each appear in a logical order. No sentence is redundant or wasted.

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 mutation tool with no output schema and no annotations, the description covers the essential operational facts: what it creates, what it returns, scheduling behavior, reversibility, rollback path, and a clear alternative for one-off products. Minor details like authentication are already present in the schema, so nothing critical is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds useful parameter-related context by enumerating supported feed formats (CSV, TSV, RSS 2.0, Atom 1.0, JSON), which informs what feed_url should point to, and clarifies the feed's ongoing sync behavior beyond individual parameter definitions.

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 states a specific action and resource: creates a scheduled product feed that imports products into a catalog from a URL. It also names the return value, feed_id, and clearly differentiates this from one-off product additions by referencing meta_ads_products_add.

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?

The description explicitly says to use meta_ads_products_add for one-off product adds and categorizes feeds as ongoing bulk sync. It also conveys that feeds run automatically on a schedule and trigger a first run shortly after creation, giving the agent clear context for when this tool is appropriate.

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