Skip to main content
Glama
rilexus

delta-mcp-prototype

by rilexus

fetch_mentions

fetch_mentions

Retrieve media mentions filtered by search, date range, language, sentiment, and more. Returns paginated results with title, url, sentiment, and virality.

Instructions

Fetch media mentions matching the specified filters. Supports filtering by search, phrase, date range, language, country, media segment, sentiment, tags, source, read/marked/critical/mailed status, inlink count, and more. Results are paginated and sortable. Returns total count and a list of mentions with title, url, media segment, published date, sentiment, virality, and link counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (max 100). Default 25.
offsetNoNumber of initial results to skip. Max offset+limit is 10000. Default 0.
phraseNoInclude only mentions matching this search query.
countryNoFilter by country code(s), comma-separated. Use 'missing' to include mentions with no country assigned.
date_toNoExclude mentions published after this ISO 8601 timestamp. Defaults to 3000-01-01T01:01:01.000Z.
tags_idNoInclude mentions tagged with at least one of the specified tag ids, comma-separated.
languageNoFilter by language code(s), comma-separated (e.g. 'en' or 'en,de').
date_fromNoExclude mentions published before this ISO 8601 timestamp (e.g. '2024-01-01' or '2024-01-01T08:00Z').
sentimentNoFilter by sentiment: -1 (negative), 0 (neutral), 1 (positive), -99 (no sentiment).
searches_idNoComma-separated list of search ids. Use '0' for all searches, a folder id for all searches in a folder, or specific search ids.0
media_segment_idNoFilter by media segment id(s), comma-separated. Available values: * 2 (Blogs) * 3 (News) * 4 (Social Networks) * 5 (Microblogs) * 6 (Web) * 7 (Forums) * 10 (Press Releases)
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses pagination, sorting, and the return value structure (total count, list with fields). However, it omits any mention of rate limits, authentication requirements, or side effects. Overall, good but not exhaustive.

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?

The description is two sentences long with no fluff. The first sentence states the purpose, and the second encapsulates the key features. It is well-structured and front-loaded.

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?

Given the tool has 11 parameters and no output schema, the description covers the main use case and return values. It could be more explicit about how filters combine (e.g., AND logic) but is largely complete for a listing tool.

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 description coverage is 100%, so every parameter is documented in the schema. The description adds no parameter-specific meaning beyond listing some filter examples, which is already covered. Baseline 3 is appropriate.

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?

The description clearly states the tool fetches media mentions and lists many filter options, making the purpose specific and distinct from the only sibling tool (current_date_and_time) which is unrelated.

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

Usage Guidelines3/5

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

The description explains what the tool does and its capabilities but does not provide explicit guidance on when to use it versus alternatives or when not to use it. Given the absence of relevant siblings, it is adequate but lacks exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rilexus/delta-mcp-prototype'

If you have feedback or need assistance with the MCP directory API, please join our Discord server