Skip to main content
Glama
nubiia-dev

MCP NewsAPI.ai

by nubiia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_trending_concepts

Read-only

Get the concepts (people, organisations, places) that are trending right now in the news — computed by comparing mentions in the last 2 days against the last 2 weeks.

Instructions

Get the concepts (people, organisations, places) that are trending right now in the news — computed by comparing mentions in the last 2 days against the last 2 weeks. Use source to switch between news, social, pr and blog (blog trends are not computed on every plan: the API then answers "not computed" and the call is still billed). Defaults to the top 10 people/organisations/places in news. Cost: 10 tokens per call regardless of count (measured live) - the priciest tool, use sparingly.

Input Schema

NameRequiredDescriptionDefault
countNoHow many trends, 1-50 (default 10).
sourceNoData source to compute trends from (default news).
concept_typesNoConcept kinds to include (default: person, org, loc). 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 / concept_types / anyOf
      Added value: +[
+  {
+    "enum": [
+      "person",
+      "org",
+      "loc",
+      "wiki"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "person",
+        "org",
+        "loc",
+        "wiki"
+      ],
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / concept_types / description
      Previous value: -"Concept kinds to include (default: person, org, loc)."New value: +"Concept kinds to include (default: person, org, loc). Accepts a single string or an array of strings."
    • removedInput schema / properties / concept_types / items
      Removed value: -{
-  "enum": [
-    "person",
-    "org",
-    "loc",
-    "wiki"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / concept_types / type
      Removed value: -"array"
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it discloses the exact cost (10 tokens per call, regardless of count), warns that blog trends may be 'not computed' yet still billed, and explains the comparison window used to compute trends. This is precisely the kind of billing and failure-mode context an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose and computation, then layers source and cost caveats. It is dense with parentheticals and could be split for readability, but every sentence carries non-redundant information.

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 the essentials for a 3-parameter read tool with no output schema: what is returned, how it is computed, source behavior, defaults, and cost. The only gap is that it doesn't describe the shape of a returned trend entry, which is minor given there is no output schema to lean on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains that `source` switches the underlying data pipeline, calls out the blog-plan caveat not visible in the enum, and restates the default result shape (top 10 people/organisations/places in news). `count` and `concept_types` are left to the schema, keeping it at 4 rather than 5.

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 and resource ('get the concepts... trending right now in the news') and even explains the computation (last 2 days vs last 2 weeks). It does not explicitly distinguish itself from the sibling `suggest_concepts`, which is the one tool an agent might confuse it with, so it stops short of a 5.

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?

Gives a clear when-to-use signal ('trending right now'), a source-selection rule, and an explicit when-not-to-overuse instruction ('the priciest tool, use sparingly'). It does not name an alternative tool for non-trending concept lookups, so it lacks the explicit alternative routing that would earn a 5.

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