meta-agent-tools

Feed search

feed_search

Read-onlyIdempotent

Search the feed index by text and filters: format, audio/video, community, namespace and year of the newest item. Find feeds by text, format, language and availability. Filter and text search run in the SAME full-text query: values inside one parameter are OR'd, different parameters are AND'd. Without q the order is by newest in the index (recentes) and next_cursor is a keyset — follow next to walk everything. With q the order is relevance and paging is by offset. We index and link; the feeds belong to whoever publishes them.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free text over name, description and domain.
`tipo`	No	rss2, rss1, atom, json (comma-separated = OR).
`limit`	No	Feeds per page, 1-50.
`midia`	No	audio, video.
`origem`	No	index, blogroll, bridge.
`recurso`	No	content, itunes, podcast, media, slash, wfw, georss.
`api_pass`	No	MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.
`retry_key`	No	Optional retry key, up to 80 ASCII characters; same read for five minutes.
`comunidade`	No	fediverse, indieweb, mastodon, friendica, wordpress, funkwhale.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

addedInput schema / properties / api_pass

Added value: +{
+  "description": "MAT-only private pass: mat_<32 random hex>_<64 random hex>. Generate and save before buying.",
+  "type": "string"
+}

addedInput schema / properties / retry_key

Added value: +{
+  "description": "Optional retry key, up to 80 ASCII characters; same read for five minutes.",
+  "type": "string"
+}

AddedSep 16, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, but the description adds behavior beyond them: keyset cursor paging without `q` vs offset paging with `q`, relevance-vs-recency ordering, and an explicit 'we index and link' ownership caveat. That is meaningful context the annotations do not carry.

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

Conciseness3/5

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

The paging and boolean logic are front-loaded and useful, but the opening two sentences ('Search the feed index by text and filters...' / 'Find feeds by text, format, language and availability') restate the same idea, and the trailing ownership line is tangential. Slightly redundant rather than wasteful.

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?

For a 9-parameter, no-output-schema search tool, the description covers the critical calling contract: paging model, ordering, filter composition, and an auth-related pass parameter. It is largely complete, with only minor gaps (the 'year'/'language' filters it mentions have no corresponding schema parameter).

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?

Schema coverage is 100%, so the schema already documents every parameter and the baseline would be 3. The description still adds value by explaining the OR/AND composition semantics across parameters and describing the cursor vs offset paging contract, which the flat schema cannot express.

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

Purpose4/5

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

The description opens with a specific verb+resource ('Search the feed index') and enumerates the filter axes, so the tool's purpose is unambiguous. It does not, however, explicitly distinguish itself from close siblings like feed_find or feed_posts, leaving the agent to infer the boundary.

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?

It gives real operational guidance: filter/text run in the same full-text query, values within a parameter are OR'd and across parameters AND'd, and it explains what to do with and without `q`. It stops short of naming a concrete alternative tool to use instead in other cases.

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

All meta-agent-tools 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?