mcp-server

set_feed_settings

DestructiveIdempotent

Set a feed's general output settings: SHIPPING cost and STOCK. Use this to change a feed's stock and shipping output settings. Send shipping and/or stock; within each object only the keys you include change (omitted keys are left as-is). shipping: {dependent_attribute (a source attribute code from list_source_attributes the cost depends on, e.g. weight/price — '' clears it), method_name (free text), intervals (the cost table — REPLACES the whole set; each row {from, to, cost} numeric with 0 <= from <= to <= 1000000 and cost >= 0; intervals:[] clears all rows)}. stock: {in_value (the value exported when a product is In stock), out_value (the value when Out of stock), availability_attribute (a source attribute code exported as availability when out of stock — '' clears it)}. Provide at least one of shipping / stock. To rename the feed use set_feed_name (the feed name is not set here). SAVE-ONLY: persists and bumps the revision but does NOT regenerate the feed — call export_feed afterwards. Read the current values from get_feed (settings). Returns {feedId, status, changed:[...], reason, revisionBefore, revisionAfter}; status is 'updated' | 'no_changes' | 'rejected' (reason: invalid_value | unknown_source_attribute | invalid_interval). project_id is OPTIONAL (inferred for a single-project customer). OVERWRITES the keys given; shipping.intervals replaces the whole table.

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>"
    },
    "name": "set_feed_settings"
  }
}

Input Schema

Name	Required	Description
`stock`	No	Stock settings; only the keys you send change.
`feed_id`	Yes
`shipping`	No	Shipping cost settings; only the keys you send change.
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: partial-update semantics for omitted keys, full replacement of shipping.intervals, save-only behavior that does not regenerate the feed, revision bumping, return shape with status values and rejection reasons, and optional project_id inference. This is consistent with destructiveHint and idempotentHint.

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?

Information is front-loaded and each section maps to a real decision the agent must make. It is dense and includes a little repetition at the end ('OVERWRITES the keys given; shipping.intervals replaces the whole table'), but the length is justified by the nested schema and mutation semantics.

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 nested mutation tool with no output schema, the description is complete: it covers update semantics, overwrite behavior, validation constraints, the need to call export_feed afterwards, the return object, and the failure statuses.

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

Parameters5/5

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

With only 50% schema description coverage, the description compensates fully: it documents the shape of shipping and stock, the clearing semantics of empty strings, the intervals replacement rule, numeric bounds for interval rows, and that project_id is optional and inferred for single-project customers.

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?

States a specific verb and resource: 'Set a feed's general output settings: SHIPPING cost and STOCK.' It also explicitly distinguishes itself from siblings by saying renaming uses set_feed_name and regeneration uses export_feed.

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?

Explains when to use it ('to change a feed's stock and shipping output settings'), requires at least one of shipping/stock, tells the agent to read current values from get_feed first, and routes rename and export to the correct sibling tools.

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

All mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?