Skip to main content
Glama

FeedShine: Shopify Google Shopping Feed

List product groups and feeds

list_feeds
Read-onlyIdempotent

List every product group and its feeds (type, format, enabled state, market binding) with each feed's latest generation run. Start here to find feed ids. Each feed carries its market name and locale, so feeds serving different languages are told apart before any text is written to them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
groupsYesOne entry per product group: groupId, groupName, collectionGids and its feeds, each with its marketName, marketLocale, marketCountry (whose prices, in their currency, a market feed sends) and latestRun

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / groups / description
      Previous value: -"One entry per product group: groupId, groupName, collectionGids and its feeds, each with its marketName, marketLocale and latestRun"New value: +"One entry per product group: groupId, groupName, collectionGids and its feeds, each with its marketName, marketLocale, marketCountry (whose prices, in their currency, a market feed sends) and latestRun"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the description only needs to add context. It does: each feed is returned with its latest generation run, plus market name and locale for disambiguation. It omits pagination/volume behavior for what could be a long list, keeping it at 4.

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?

Two sentences, both front-loaded with the most important information (what is listed, then why the locale/market data matters). The closing clause about 'before any text is written to them' is slightly indirect but earns its place as a usage rationale.

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?

With an output schema present, return values need no prose explanation, and with zero parameters there is nothing else to document. The description covers purpose, entry-point role, and the disambiguating fields; only minor details like ordering or handling of groups with no feeds are absent.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on inputs.

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 ('List every product group and its feeds') and enumerates the returned attributes (type, format, enabled state, market binding, latest generation run). The phrase 'Start here to find feed ids' implicitly separates it from get_feed, which takes an id.

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

Usage Guidelines4/5

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

Gives clear entry-point guidance ('Start here to find feed ids') and a practical rationale for inspecting market name/locale before writing text to a feed. It stops short of naming an explicit alternative or stating when not to use it, so it lands below a full 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources