Pollar News

List top Pollar news

list_top_news

Read-only

Lists Pollar's current leading news events, ranked by freshness and editorial momentum. Use for broad requests for current headlines with no named subject, place, or country. For a subject or geographic request, use search_news instead. Optionally filters by a taxonomy dot-path such as 'world.politics'; call list_categories first when the category is unknown.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`locale`	No		en
`category`	No	Taxonomy dot-path, e.g. 'world.politics'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "categoryPath": {
+            "items": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "string"
+              },
+              {
+                "type": "string"
+              }
+            ],
+            "type": "array"
+          },
+          "id": {
+            "type": "string"
+          },
+          "imageSource": {
+            "type": "string"
+          },
+          "imageUrl": {
+            "type": "string"
+          },
+          "lead": {
+            "type": "string"
+          },
+          "modifiedAt": {
+            "type": "string"
+          },
+          "publishedAt": {
+            "type": "string"
+          },
+          "shortHeadline": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "sourceCount": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "slug",
+          "title",
+          "shortHeadline",
+          "lead",
+          "imageUrl",
+          "imageSource",
+          "publishedAt",
+          "modifiedAt",
+          "categoryPath",
+          "sourceCount",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedJun 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true, and the description adds that results are ranked by freshness and editorial momentum. No mention of other behaviors like pagination, but the output schema likely covers return structure.

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?

Four sentences, no wasted words. Front-loaded with purpose and ranking, then usage guidance, alternative, and optional filter info. Highly efficient.

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?

Covers purpose, usage, and category filtering. Does not explicitly mention limit or locale, but standard defaults are in schema. Output schema exists so return values are documented. Slight gap in not explaining how to handle large result sets.

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?

The description adds meaning for the category parameter (taxonomy dot-path and hint to call list_categories), but does not address limit or locale beyond what the schema provides. Schema coverage is only 33%, so partial compensation.

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 it lists current leading news events ranked by freshness and editorial momentum, and explicitly distinguishes from search_news for requests with a named subject, place, or country.

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

Usage Guidelines5/5

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

Explicitly specifies when to use (broad headline requests) and when not (named subject/place/country) with a direct sibling alternative (search_news). Also advises to call list_categories when the category is unknown.

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

All Pollar News tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?