Skip to main content
Glama
Sign In

Emberfeed

by com.emberfeed
OverviewDiscussionsAdmin

Import a new feed from a source XML URL

create_feed

Fetches the XML or CSV/TSV feed at sourceUrl, parses it, and stores it under the calling user. Auto-detects the catalog type from the field shape. Set targetPlatform to the channel you want to serve to (meta/google/tiktok/heureka/zbozi). Returns the new feed id + served URL. IMPORTANT: respects the free-tier 1-feed cap — fails with planReason if the user has hit it.

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": {
      "sourceUrl": "<sourceUrl>",
      "name": "<name>"
    },
    "name": "create_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable label shown in the dashboard.
sourceUrlYesPublic URL of the XML (RSS, Atom, SHOP) or CSV/TSV feed to import.
targetPlatformNoWhich ad channel this feed serves — drives required-field validation.meta

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare write, open-world, non-idempotent and non-destructive, and the description adds materially: network fetch of an external URL, automatic catalog-type detection from field shape, the free-tier 1-feed cap with a `planReason` failure payload, and the shape of the success return (new feed id + served URL). These are quota and failure behaviors the annotations cannot express.

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?

Four short sentences, each doing distinct work: action, auto-detection behavior, parameter guidance, return value, and the capped-plan failure mode, with the critical constraint flagged up front by 'IMPORTANT'. No filler or restatement of the title.

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 three-parameter import tool with no output schema, the description supplies the return shape (feed id + served URL) and the main error path (plan cap → planReason), which is exactly what an agent needs before invoking it. Nothing material is left undisclosed.

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

Parameters3/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 restates the enum values for `targetPlatform` (already enumerated in the schema) and the schema already explains that it drives required-field validation, so almost no new per-parameter meaning is added beyond what structured fields carry.

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 chain (fetches, parses, stores) against a named resource (`sourceUrl` feed), and the object is clearly a new feed owned by the calling user. It is trivially distinguishable from siblings like get_feed, list_feeds, and refresh_feed, which read or re-fetch rather than import.

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 triggering context: import a feed from a public XML/CSV/TSV URL, choose `targetPlatform` for the channel being served. It also discloses the precondition that the caller must be under the free-tier 1-feed cap. It stops short of explicitly routing to alternatives (e.g., refresh_feed to re-pull, update_feed to change platform), so it is not a full when/when-not guide.

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

All Emberfeed toolsInspect
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