Skip to main content
Glama

NewzAI News MCP server

by ai.newzai.api
OverviewDiscussionsAdmin

update_user_preferences

Update news preferences for the authenticated user. Each preference is defined by news category(or search parameter), region, output language. Optional values include last_n_hours for recency filter, search_type, and enable_decay. Leave search_type as auto (default) — the system will classify the best type from the category. Login is required to access this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the preference to update
preferenceYesPreference to update for the user

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
regionYes
categoryYes
languageYes
search_typeYes
enable_decayYes
last_n_hoursYes
similarity_thresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / preference / properties / region / enum
      Added value: +[
+  "india",
+  "united-states",
+  "united-kingdom",
+  "japan",
+  "international"
+]
    • addedOutput schema / properties / region / enum
      Added value: +[
+  "india",
+  "united-states",
+  "united-kingdom",
+  "japan",
+  "australia",
+  "canada",
+  "germany",
+  "international"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / preference / properties / search_type / default
      Previous value: -"hybrid"New value: +"auto"
    • changedInput schema / properties / preference / properties / search_type / description
      Previous value: -"Search algorithm to use for this preference. Optional. Default is HYBRID. Use HYBRID for a mix of semantic and keyword search, SPARSE for keyword-preferred search, VECTOR for semantic-preferred search, and EXACT when an exact match is required (case and language sensitive)."New value: +"Search algorithm to use for this preference. Defaults to auto — the system classifies the best type from the category. You can also specify: hybrid for semantic + keyword mix, sparse for keyword-preferred, vector for semantic-preferred, exact for precise title match."
    • changedInput schema / properties / preference / properties / search_type / enum
      Previous value: -[
-  "vector",
-  "hybrid",
-  "sparse",
-  "exact"
-]New value: +[
+  "vector",
+  "hybrid",
+  "sparse",
+  "exact",
+  "auto"
+]
    • changedOutput schema / properties / search_type / enum
      Previous value: -[
-  "vector",
-  "hybrid",
-  "sparse",
-  "exact"
-]New value: +[
+  "vector",
+  "hybrid",
+  "sparse",
+  "exact",
+  "auto"
+]
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate a write operation (readOnlyHint=false). Description adds login requirement and notes about default behavior, but does not detail side effects or error scenarios.

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?

Three sentences, front-loaded purpose, but the second sentence is slightly verbose. Overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple update tool with output schema present. Missing details on return value or error conditions, but sufficient given constraints.

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%, but description adds value by summarizing fields and giving a specific tip about search_type defaulting to auto. Helps agent understand usage beyond raw schema.

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?

Description clearly states 'Update news preferences for the authenticated user' and lists major fields. However, it does not distinguish from the sibling tool 'set_user_preferences' which might create new preferences instead of updating existing ones.

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

Usage Guidelines3/5

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

Provides guidance on search_type defaults and login requirement, but lacks explicit when-to-use vs alternatives like get_user_preferences or set_user_preferences.

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

All NewzAI News MCP server toolsInspect
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