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.
`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.

Changed1 schema field changedOct 15, 2026

removedInput schema / properties / api_pass

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

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

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds substantial behavior beyond that: OR within parameters versus AND across parameters, pagination mode switching based on q, keyset vs offset, following next to walk everything, and the index/link ownership model.

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?

The description is front-loaded with the core purpose and then proceeds to query and pagination behavior. It is dense and largely waste-free, though the first two sentences overlap slightly by both summarizing the searchable dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter search tool with no output schema, the description covers filtering, query combination, ordering, and pagination well. It does not describe the return shape or result fields, and the retry_key behavior is left entirely to the schema. Adequate but with clear gaps for a no-output-schema tool.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful query semantics beyond the schema by explaining that values within one parameter are OR'd while different parameters are AND'd, and by describing q as free text over name, description, and domain. It also references a 'year of the newest item' filter that is not clearly represented in the schema, a small mismatch.

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 states a specific verb and resource: search the feed index / find feeds by text and filters. It lists concrete filter dimensions such as format, audio/video, community, and availability. It does not explicitly distinguish itself from the sibling feed_find, so it falls short of a 5.

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 explains the key usage conditions: without q the order is newest-first with keyset pagination via next, while with q the order is relevance-based with offset pagination. It also states that text and filters run in the same full-text query. However, it gives no explicit when-not-to-use guidance or named alternatives.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?