Skip to main content
Glama

Tavily (Unofficial)

Tavily News

tavily_news
Read-onlyIdempotent

Recent NEWS coverage with FULL ARTICLE TEXT, "latest news about <company/person/topic>", "news coverage of X this week", "what are people reporting about X", "recent headlines on X". Returns a synthesized answer plus ranked articles each carrying title, url, publication content, and a relevance score, the full text, not just a headline, so the calling agent can quote and cite. Freshness-windowed via days (default 7). This is the premium news path (Tavily, funded key, no per-IP throttle, no shared free-tier quota); prefer it when the question asks what is being REPORTED about a specific entity or topic.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Anthropic"
    },
    "name": "tavily_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to search (default 7, max 30).
queryYesThe entity or topic to get news about, e.g. "Anthropic", "GLP-1 drug pricing".
_apiKeyNoOptional, your own Tavily API key for higher limits; omit to use the shared Pipeworx key.
max_resultsNoMaximum number of articles (default 5, max 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Tavily API key for higher limits; omit to use the shared Pipeworx key."New value: +"Optional, your own Tavily API key for higher limits; omit to use the shared Pipeworx key."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered; the description adds genuinely new context instead of repeating it. It discloses the return shape (synthesized answer plus ranked articles with title, url, content, relevance score), the freshness default of 7 days, and the quota profile (funded key, no per-IP throttle, no shared free-tier quota). What it omits is failure modes for empty or paywalled coverage.

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?

The capability and the full-text guarantee are front-loaded, and the example queries earn their place by disambiguating intent. The sentence is long and comma-chained with a mild redundancy in "the full text, not just a headline, so the calling agent can quote and cite," but no sentence is filler.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of describing the return payload, and it does so at the field level while also covering freshness defaults and quota behavior. For a four-parameter read-only search tool whose schema is fully documented, nothing an agent needs in order to call it correctly is missing.

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% and each of the four parameters already carries its own description, so the schema does the heavy lifting. The description restates the `days` default of 7 and frames `query` as an entity or topic, but adds no syntax, bounds, or interaction detail beyond what the schema states.

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?

States a specific verb and resource ("Recent NEWS coverage with FULL ARTICLE TEXT") and backs it with concrete query phrasings like "latest news about <company/person/topic)" and "recent headlines on X". The "premium news path" framing plus the explicit "what is being REPORTED about a specific entity" scoping separates it from the generic tavily_search sibling without needing a schema read.

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?

The description gives a clear selection rule: prefer this when the question asks what is being reported about a specific entity or topic, and it supplies several trigger phrasings. It lacks an explicit negative case (what to use for non-news or general web queries), so the agent must infer that boundary from the sibling name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.