Search Polymath News
search_newsSearch current news for a specific reader. Covers technology, AI, business, policy, and media and entertainment (about 500 curated sources, not all news). Returns one list of stories, best match first: events, each grouped across the outlets covering it, with every article (publisher, date, link), the lead article's excerpt, the names in it, and which of your terms it matches and how well (0 to 1). Then Polymath reports, with title, insight and link. Put topics in "interests": 3 to 8 specific topics, named the way a news desk would ("AI regulation", "data centers"). The name of a person or a company works as an interest too ("Nvidia"). Each interest gets its fair share of the list, and the reply says what each one found, including nothing. "query" is for keywords. "profile" says who you work for: it tailors reports and rarely selects stories by itself. "since" returns only what is new or updated after a time; every reply gives next_since, the value to pass next time. With no arguments it returns the top stories right now. No API key was sent, so this is a trial: 1 searches a day, up to 3 stories per search, report titles and links only.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "search_news"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Keywords or a short question, for example "EU AI Act enforcement" or "who is buying data centers". | |
| since | No | Only what is new since this time (ISO 8601, for example "2026-11-09T07:00:00Z"). Pass the next_since value from your previous search_news reply. Overrides since_days. Stories are marked new or updated. | |
| detail | No | Less or more text. brief (default): every story with every article (publisher, date, link), the lead article's excerpt and the names in it. full: the same, plus every article's excerpt and a summary of each Polymath report. | |
| profile | No | Who you are working for, in one or two sentences, for example "a mid-size US law firm with a technology practice". The profile tailors reports. It rarely selects stories by itself, so put the topics in "interests". | |
| interests | No | Three to eight specific topics this reader cares about, which you infer from the profile, for example ["AI regulation", "data centers", "Nvidia"]. Name each topic the way a news desk would. The name of a person or a company works as an interest too. Each interest gets its fair share of the results, and every story says which interests it matches and how well, so specific topics work far better than a profile alone. | |
| since_days | No | How many days back to look. Default 7 for stories and 30 for reports. Stories go back at most 30 days, reports 90. | |
| max_results | No | Most stories and most reports to return, each. Default 8. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| notes | Yes | ||
| since | No | ||
| terms | No | Each of your terms that selected results, with what it returned. | |
| detail | Yes | ||
| include | No | Older replies only. | |
| matcher | No | Present when the results come from Polymath's own search (the default). | |
| reports | Yes | ||
| stories | Yes | ||
| coverage | No | Older replies only. | |
| next_since | Yes | Pass as "since" on the next call to get only what is new. | |
| signup_url | No | ||
| balance_usd | No | ||
| charged_usd | No | ||
| top_stories | No | True when the list is the top stories: nothing was asked for, or only a profile that matched nothing. | |
| window_days | Yes | ||
| used_free_search | No | ||
| trial_searches_left | No | ||
| free_searches_remaining | No |