Skip to main content
Glama
nubiia-dev

MCP NewsAPI.ai

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

suggest_sources

Read-only

Resolve a publication name or domain to news source URIs (e.g. "bbc.co.uk"). Pass the uri as source_uris to search_articles / search_events. Does not consume search tokens.

Instructions

Resolve a publication name or domain to news source URIs (e.g. "bbc.co.uk"). Pass the uri as source_uris to search_articles / search_events. Does not consume search tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoResult page, from 1 (default 1).
countNoMax suggestions, 1-50 (default 10).
prefixYesText typed so far (a name or the start of one), e.g. "Telef" or "bbc".
data_typesNoRestrict to sources of these content types (default: all). Accepts a single string or an array of strings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.2
    • addedInput schema / properties / data_types / anyOf
      Added value: +[
+  {
+    "enum": [
+      "news",
+      "pr",
+      "blog"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "news",
+        "pr",
+        "blog"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / data_types / description
      Previous value: -"Restrict to sources of these content types (default: all)."New value: +"Restrict to sources of these content types (default: all). Accepts a single string or an array of strings."
    • removedInput schema / properties / data_types / items
      Removed value: -{
-  "enum": [
-    "news",
-    "pr",
-    "blog"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / data_types / type
      Removed value: -"array"
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context that it 'does not consume search tokens,' but does not describe the return format or pagination, which are left implicit.

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?

Two sentences with zero waste, front-loaded with the purpose and followed by actionable integration guidance. Every sentence earns its place.

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?

For a read-only suggestion lookup with full schema coverage and no output schema, the description gives enough: what it returns (source URIs), how to use them downstream, and the token-cost note. A minor gap remains around result list structure and pagination, but that is largely inferable from the page/count parameters.

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 all four parameters (prefix, page, count, data_types) are already documented. The description adds no parameter-level detail beyond the example 'bbc.co.uk', so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Resolve) and resource (publication name or domain to news source URIs), with an example. It does not explicitly distinguish itself from sibling suggestion tools like suggest_concepts or suggest_categories, but the resource is clear enough for an agent to pick it correctly.

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

Usage Guidelines4/5

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

Explains what to do with the result: 'Pass the `uri` as source_uris to search_articles / search_events.' This gives clear downstream context without naming when not to use it or alternatives among the suggest_* siblings.

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

Deploy Server

Other Tools