APIVerve

Ticker News

TickerNews

Read-only

Ticker News: Ticker News is a stock news API that returns the latest news stories about one ticker symbol: US stocks and ETFs, stocks on 18 international markets, cryptocurrencies, futures and currency pairs. Each story comes with its headline, link, source, publisher and publication time, and is tagged as directly about the company or as a related market story. Paid plans add story summaries, headline tone and more stories per call. (Cost: 2 credits)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "TickerNews"
  }
}

Input Schema

Name	Required	Description	Default
`since`	No	Return only stories published at or after this date or date-time (ISO 8601), for example 2026-10-01 or 2026-10-01T14:00:00Z.
`market`	No	The market of the listing, when the ticker trades in more than one: a two-letter market code, CRYPTO, FUTURES or FX. Defaults to the US listing.
`ticker`	Yes	The ticker symbol to get news for, for example AAPL, BRK.B, 7203 or SHEL. A suffix such as BP.L, a coin pair such as BTC-USD, a contract such as CL=F or a currency pair such as EUR/USD picks that market.
`relevance`	No	direct returns only stories whose headline or summary names the company or ticker; all also returns the sector round-ups and peer stories the news feeds carry for the ticker.	direct

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: a fixed cost of 2 credits, plan-dependent payload differences (summaries, tone, more stories per call), and that stories are tagged as directly-about the company versus related market stories.

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?

One efficient paragraph that front-loads the core purpose before coverage, payload and cost details. Minor waste in the opening 'Ticker News: Ticker News is...' repetition of the name and title, but nothing else is padded.

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?

With full schema coverage, an output schema and rich annotations, the remaining burden is mainly about cost and payload variability, both of which are stated. What an agent needs to call this correctly is essentially present.

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%, with each parameter documented including ISO 8601 format for 'since' and market-suffix conventions for 'ticker'. The description only echoes the direct/related tagging idea already present in the 'relevance' schema text, so it adds little beyond the structured fields.

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: returns the latest news stories for one ticker, and enumerates the asset classes covered (US stocks/ETFs, 18 international markets, crypto, futures, FX). That scoping distinguishes it implicitly from broad siblings like WorldNews or SECFilings, though no sibling is named directly.

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?

Usage is implied by the scope statement (single-ticker news retrieval) and the relevance default of 'direct' is surfaced, but there is no explicit when-to-use/when-not guidance or pointer to an alternative tool for general or multi-ticker news.

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

All APIVerve 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.