NYTimes Article Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NYTIMES_API_KEY | Yes | Your New York Times API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_articlesC | Search NYTimes articles from the last 30 days based on a keyword |
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
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search_articles' has a clearly defined and distinct purpose.
The single tool name follows a clear verb_noun pattern ('search_articles'), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and appropriate.
One tool is too few for a server with the apparent scope of 'NYTimes Article Search,' which suggests a domain that could benefit from additional operations like filtering by date, retrieving article details, or accessing different sections. A single search tool feels thin and limits functionality.
The tool surface is severely incomplete for the domain. While search is a core function, there are obvious gaps such as the inability to retrieve full article content, filter beyond keywords, or access other NYTimes data like sections or authors. This will likely cause agent failures when more comprehensive interactions are needed.