agenticfeed
Server Details
Match shopper intent to a merchant's products and fetch live price, stock and product Q&A.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- bluestratus/agenticfeed
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 4 of 4 tools scored.
Each tool has a clearly distinct purpose: find_merchant resolves a domain to a merchant ID, list_products shows the catalog, get_product provides full details for a specific product, and search_products finds products matching a shopper's intent. No overlap.
All tool names follow the consistent verb_noun pattern in snake_case: find_merchant, get_product, list_products, search_products. Perfect consistency.
Four tools are appropriate for a product feed server covering the essential workflow: identify merchant, browse catalog, get details, and search by intent. The count is well-scoped.
The tool set covers the core operations for querying product data: merchant resolution, catalog listing, detailed product retrieval, and intent-based search. There are no obvious gaps for a read-only feed service.
Available Tools
4 toolsfind_merchantInspect
Resolve a merchant's website domain to their Agenticfeed merchant ID and confirm they publish an Agentic Feed. Call this first when you only know a store's domain; use the returned merchant_id with get_product or the discovery feeds.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Merchant website domain or URL, e.g. "boardgameextras.co.uk". |
get_productInspect
Get full detail for a single product by merchant_id and product_id: name, price, currency, availability, image, and the buyer questions, problems, and use cases it maps to. Returns a schema.org Product.
| Name | Required | Description | Default |
|---|---|---|---|
| merchant | Yes | Agenticfeed merchant ID (customer GUID), e.g. "a9a8378c94". | |
| product_id | Yes | Product ID (product GUID) within that merchant's catalog. |
list_productsInspect
List a merchant's in-stock products (product_id, title, price, availability, url). Call after find_merchant to see the catalogue, then get_product for full detail. For a specific shopper need, prefer search_products.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max products to return (default 50, max 200). | |
| merchant | Yes | Agenticfeed merchant ID (customer GUID), e.g. "a9a8378c94". |
search_productsInspect
Find a merchant's products that match a shopper's need, question, problem, or use case. Pass the buyer intent in natural language (e.g. "a light strategy game for 4 players under thirty pounds"); returns ranked in-stock products with the reason each fits, drawn from Agenticfeed's intent mapping (questions, problems, use cases). Call find_merchant first to get the merchant ID.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results to return (default 5, max 10). | |
| query | Yes | The shopper's need, in natural language. | |
| merchant | Yes | Agenticfeed merchant ID (customer GUID). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!