Skip to main content
Glama
Sign In
reddit-ads-mcp

reddit-ads-mcp

by filippofinke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update product feed

reddit_ads_update_product_feed

Update an existing Reddit Ads product feed's name, URL, credentials, mode, or schedule.

Instructions

Update a product feed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feed_id": "<feed_id>",
      "data": "<data>"
    },
    "name": "reddit_ads_update_product_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesSent as {"data": {...}}. Fields: name, url, username, password, mode, schedule.
feed_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is partly covered. However, the description adds zero behavioral context: it does not say what fields are mutable, whether omitted fields are preserved or cleared, or what happens on an unknown feed_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, but that brevity comes from under-specification rather than efficiency. The one sentence is a restatement of the name and does not earn its place.

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

Completeness1/5

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

This is a mutation tool with a nested data object, 50% schema coverage, and no output schema. Nothing covers required permissions, partial-update behavior, or return values, so an agent cannot call it correctly with confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: feed_id has no description at all, while the nested data object does list its fields (name, url, username, password, mode, schedule). The description contributes nothing to compensate, leaving the identifier parameter and update-semantics unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the title almost verbatim: 'Update a product feed.' It names a verb and resource but adds nothing that distinguishes it from siblings such as reddit_ads_update_product_set, reddit_ads_update_catalog, or reddit_ads_create_product_feed. This is effectively a tautology.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, no prerequisites, and no mention of alternatives or when-not-to-use. An agent has no basis to choose it over any other update tool in the family.

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