Journalist and Media List Builder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token; a tool call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_journalistsA | Build a media list of journalists who recently wrote about given topics or beats. Give topics (1 to 20; quotes for an exact phrase) and optionally since_days, country, outlets_include, outlets_exclude, min_articles, and max_journalists. The actor reads recent Google News articles through the Mamba Labs News and Media Mention Monitor, reads each article page's byline, and returns one row per journalist and outlet: journalist_name, outlet, outlet_domain, author_page_url, x_handle, article_count, latest_article_title, latest_article_url, latest_published_at, topics_matched, and article_urls as evidence. Press release wires and desk or agency bylines are left out. No emails are returned. When none is found, one free summary row says why. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per journalist returned plus the news run's price per article read. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of overlap or misselection. The tool's purpose (build a media list of journalists by topic) is clearly stated and unambiguous.
find_journalists follows a clear verb_noun snake_case convention. With only one tool there is no pattern to compare against, so consistency cannot be fully demonstrated, but the name itself is predictable and descriptive.
A single tool is thin for a server framed as a 'media list builder.' The one tool is well-scoped and parameter-rich, but the surface feels narrow and borderline minimal for the apparent domain.
The tool covers the core workflow (topics in, journalist rows with evidence out) with useful filters and clear empty/error handling. However, there are no companion operations such as saving/exporting a list, refining an existing list, or fetching a single journalist's details, leaving potential dead ends.