Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

tickerbot_search_news

Search stock and crypto news by full-text keywords, ticker, or universe, filtered by date range, relevance, and sentiment. Returns article rows or grouped rollups.

Instructions

Deprecated: works until 2027-01-12. Same as tickerbot_query_news; call that instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
qNoWHERE clause over news articles. Max 4000 chars. Required unless `search`, `ticker`, `universe`, `from` or `to` is present. Takes every article field under Returns except `mentions`, plus the per-mention fields `ticker`, `relevance`, `sentiment_score` and `sentiment` (one article per mention).
toNoArticles strictly before this instant, in the same strict ISO subset as `from` (as on `/v2/events`). A bare `YYYY-MM-DD` means through the end of that day (the ET calendar day), so `from` and `to` on the same date return that day.
dirNoSort direction. Values: asc: Ascending: smallest or earliest first. desc: Descending: largest or most recent first.desc
fromNoEarliest `time_published` (inclusive), in strict ISO: `YYYY-MM-DD` or `YYYY-MM-DDTHH:MM[:SS]Z`. A bare date starts at 00:00 ET that day.
limitNoPage size (articles) / max groups (a `group_by` rollup). Articles take up to 1000 until 2027-01-12, then 100, and page the rest with `next_cursor`. A rollup does not page: it returns up to `limit` groups, every group up to 1000 by default, and sets `truncated: true` when there are more. A larger value is clamped to the max, not an error; see Deprecations.
orderNoSort by a bare field name or SELECT alias only (put expressions in `select` and order by their alias). Defaults to `time_published` (articles) or `volume` (rollups; with your own `select` that has no `volume` column, its last column's alias).
cursorNoFrom a prior response's `next_cursor`. Send it with the same params as the first page (`limit` may change). It holds the position and pins the read: a page whose params differ from the first page's, or a cursor sent alone, is a 400 naming the param to send.
havingNoOnly with `group_by`. HAVING clause on the rollup (max 1000 chars).
searchNoFull-text search over `title` + `summary`, in websearch grammar: `nvidia earnings` (all words), `"price target"` (phrase), `chips OR semiconductors`, `-crypto` (negation). Max 200 chars. ANDs with `q` and the other filters. Language-stemmed English.
selectNoFields or expressions to return (max 2000 chars). Defaults to the article row (no `group_by`) or `<group_by keys>, COUNT(*) AS volume` (with `group_by`). `*` returns every article field under Returns plus `mentions` (on a per-mention row, the mention's four fields too). `mentions` is selectable on its own.
tickerNoOne ticker or a comma list (up to 50): articles that mention any of them. Not combinable with `universe`. Per-mention rows still list every ticker an article mentions; put `ticker = 'NVDA'` in `q` for one ticker's rows.
group_byNoComma-separated group keys, 1-6 (max 1000 chars); the response becomes rollups. `ticker` rolls up per ticker mentioned. Name a key with `AS` to choose its JSON key; an un-named expression is named for you.
universeNoScope to a built-in universe (`top_10`, `top_100`) or one of your own, by id. An unknown one answers 200 with no results and its id in `not_found`. Articles that mention any member. Not combinable with `ticker`.
min_relevanceNoOnly with `ticker` or `universe`. Keeps an article only when it is about one of the tickers, meaning that ticker's `relevance` (0 to 1) is at least this value. `0.8` drops passing mentions. Omitted: every article that mentions them. `400` without a ticker scope; in `q`, filter the mention itself: `ticker = 'NVDA' AND relevance >= 0.8`.

Output Schema

NameRequiredDescriptionDefault
as_ofYesServer time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).
countYesThe rows in `results` on this page: articles, one row per mention on a per-mention read, or groups on a rollup.
queryYesYour request echoed, each param with its effective value, in the documented param order. `ticker` is the ticker scope as a list. A param you did not send is `null`.
resultsYesArticles (one per article per mention when you name a per-mention field), or rollups when you passed `group_by`.
not_foundNoWith `ticker` or `universe`: what you named that does not exist: the symbols we do not track, in request order, or an unknown `universe` id; an empty array when every one was found. A typo here is listed, not read as "no news".
truncatedNoRollups only (`group_by`): `true` when `limit` cut the group list.
_advisoriesNoPresent only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).
next_cursorYesOpaque token for the next page; `null` on the last page. Pass it back as `cursor` with the same params. Rollups do not page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv0.4.1
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor."New value: +"From a prior response's `next_cursor`. Send it with the same params as the first page (`limit` may change). It holds the position and pins the read: a page whose params differ from the first page's, or a cursor sent alone, is a 400 naming the param to send."
    • addedInput schema / properties / dir / default
      Added value: +"desc"
    • changedInput schema / properties / dir / description
      Previous value: -"Sort direction."New value: +"Sort direction. Values: asc: Ascending: smallest or earliest first. desc: Descending: largest or most recent first."
    • removedInput schema / properties / dir / enum
      Removed value: -[
      -  "asc",
      -  "desc"
      -]
    • addedInput schema / properties / dir / pattern
      Added value: +"^\\s*([aA][sS][cC]|[dD][eE][sS][cC])\\s*$"
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Earliest `time_published` (inclusive), in strict ISO: `YYYY-MM-DD` or `YYYY-MM-DDTHH:MM[:SS]Z`. A bare date starts at 00:00 ET that day.",
      +  "type": "string"
      +}
    • changedInput schema / properties / group_by / description
      Previous value: -"Comma-separated columns for aggregation. Alias a key with `AS` to name its JSON key; un-named expressions are named for you."New value: +"Comma-separated group keys, 1-6 (max 1000 chars); the response becomes rollups. `ticker` rolls up per ticker mentioned. Name a key with `AS` to choose its JSON key; an un-named expression is named for you."
    • changedInput schema / properties / having / description
      Previous value: -"WHERE-style filter on aggregates. Requires group_by."New value: +"Only with `group_by`. HAVING clause on the rollup (max 1000 chars)."
    • addedInput schema / properties / limit / default
      Added value: +50
    • changedInput schema / properties / limit / description
      Previous value: -"Page size."New value: +"Page size (articles) / max groups (a `group_by` rollup). Articles take up to 1000 until 2027-01-12, then 100, and page the rest with `next_cursor`. A rollup does not page: it returns up to `limit` groups, every group up to 1000 by default, and sets `truncated: true` when there are more. A larger value is clamped to the max, not an error; see Deprecations."
    • addedInput schema / properties / min_relevance
      Added value: +{
      +  "description": "Only with `ticker` or `universe`. Keeps an article only when it is about one of the tickers, meaning that ticker's `relevance` (0 to 1) is at least this value. `0.8` drops passing mentions. Omitted: every article that mentions them. `400` without a ticker scope; in `q`, filter the mention itself: `ticker = 'NVDA' AND relevance >= 0.8`.",
      +  "type": "number"
      +}
    • changedInput schema / properties / order / description
      Previous value: -"Sort column or SELECT alias. Default time_published (non-aggregate) or volume (aggregate)."New value: +"Sort by a bare field name or SELECT alias only (put expressions in `select` and order by their alias). Defaults to `time_published` (articles) or `volume` (rollups; with your own `select` that has no `volume` column, its last column's alias)."
    • changedInput schema / properties / q / description
      Previous value: -"SQL WHERE on news_article. Optional when search or a scoping param is present."New value: +"WHERE clause over news articles. Max 4000 chars. Required unless `search`, `ticker`, `universe`, `from` or `to` is present. Takes every article field under Returns except `mentions`, plus the per-mention fields `ticker`, `relevance`, `sentiment_score` and `sentiment` (one article per mention)."
    • changedInput schema / properties / search / description
      Previous value: -"Full-text search over title+summary (websearch grammar: \"apple earnings\", quoted phrases, OR, -negation). ANDs with q and the scoping params."New value: +"Full-text search over `title` + `summary`, in websearch grammar: `nvidia earnings` (all words), `\"price target\"` (phrase), `chips OR semiconductors`, `-crypto` (negation). Max 200 chars. ANDs with `q` and the other filters. Language-stemmed English."
    • changedInput schema / properties / select / description
      Previous value: -"Comma-separated columns to include. Defaults to a slim set."New value: +"Fields or expressions to return (max 2000 chars). Defaults to the article row (no `group_by`) or `<group_by keys>, COUNT(*) AS volume` (with `group_by`). `*` returns every article field under Returns plus `mentions` (on a per-mention row, the mention's four fields too). `mentions` is selectable on its own."
    • addedInput schema / properties / ticker
      Added value: +{
      +  "description": "One ticker or a comma list (up to 50): articles that mention any of them. Not combinable with `universe`. Per-mention rows still list every ticker an article mentions; put `ticker = 'NVDA'` in `q` for one ticker's rows.",
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Articles strictly before this instant, in the same strict ISO subset as `from` (as on `/v2/events`). A bare `YYYY-MM-DD` means through the end of that day (the ET calendar day), so `from` and `to` on the same date return that day.",
      +  "type": "string"
      +}
    • addedInput schema / properties / universe
      Added value: +{
      +  "description": "Scope to a built-in universe (`top_10`, `top_100`) or one of your own, by id. An unknown one answers 200 with no results and its id in `not_found`. Articles that mention any member. Not combinable with `ticker`.",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "q"
      -]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "_advisories": {
      +      "description": "Present only when the response carried a warning: `deprecated` (since, sunset_on, successor, warning; on a deprecated tool, successor names the tool to call), `rate_limit` (warning, retry_after_seconds, limit, remaining, reset_epoch_s) or `monthly_quota` (warning, limit, remaining, reset_epoch_s).",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "as_of": {
      +      "description": "Server time this response was assembled (ISO 8601); on an as-of read, the instant you asked for (As-of).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "count": {
      +      "description": "The rows in `results` on this page: articles, one row per mention on a per-mention read, or groups on a rollup.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "next_cursor": {
      +      "description": "Opaque token for the next page; `null` on the last page. Pass it back as `cursor` with the same params. Rollups do not page.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "not_found": {
      +      "description": "With `ticker` or `universe`: what you named that does not exist: the symbols we do not track, in request order, or an unknown `universe` id; an empty array when every one was found. A typo here is listed, not read as \"no news\".",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "query": {
      +      "description": "Your request echoed, each param with its effective value, in the documented param order. `ticker` is the ticker scope as a list. A param you did not send is `null`.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "results": {
      +      "description": "Articles (one per article per mention when you name a per-mention field), or rollups when you passed `group_by`.",
      +      "items": {
      +        "properties": {
      +          "authors": {},
      +          "banner_image": {},
      +          "category": {},
      +          "created_at": {},
      +          "id": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "mentions": {
      +            "items": {
      +              "properties": {
      +                "relevance": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "sentiment": {
      +                  "description": "One of: `Bearish`, `Somewhat-Bearish`, `Neutral`, `Somewhat-Bullish`, `Bullish`.",
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "sentiment_score": {
      +                  "type": [
      +                    "number",
      +                    "null"
      +                  ]
      +                },
      +                "ticker": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                }
      +              }
      +            },
      +            "type": [
      +              "array",
      +              "null"
      +            ]
      +          },
      +          "overall_sentiment_label": {
      +            "description": "One of: `Bearish`, `Somewhat-Bearish`, `Neutral`, `Somewhat-Bullish`, `Bullish`.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "overall_sentiment_score": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "relevance": {},
      +          "sentiment": {
      +            "description": "One of: `Bearish`, `Somewhat-Bearish`, `Neutral`, `Somewhat-Bullish`, `Bullish`."
      +          },
      +          "sentiment_score": {},
      +          "source": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "source_domain": {},
      +          "summary": {},
      +          "ticker": {},
      +          "tickers": {
      +            "type": [
      +              "array",
      +              "null"
      +            ]
      +          },
      +          "time_published": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "topics": {},
      +          "url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        }
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "truncated": {
      +      "description": "Rollups only (`group_by`): `true` when `limit` cut the group list."
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "query",
      +    "count",
      +    "next_cursor",
      +    "results"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does surface the most important behavioral trait: deprecation with an explicit expiry. However, it says nothing about read-only semantics, rate limits, or the fact that supported limits shrink (1000 to 100 articles) at the sunset date, which lives only in the schema.

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 short clauses, front-loaded with 'Deprecated', and every word carries actionable information (status, expiry, replacement). Nothing to trim and nothing missing for a redirect-only tool.

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 deprecated alias with a rich 14-parameter schema and an output schema, the description supplies exactly what the agent cannot get from structured fields: deprecation status, expiry date, and the replacement target. It need not repeat the full query documentation because the named successor owns it.

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% across all 14 parameters, so the schema already documents query grammar, ISO date semantics, cursor pinning and clamping behavior. The description adds no parameter meaning whatsoever, which is acceptable at full coverage but earns only the baseline.

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?

The description does not restate the verb/resource itself, but defines the tool precisely by equivalence ('Same as tickerbot_query_news') plus a hard sunset date, which is the operative fact for an agent. Combined with the name, there is no ambiguity about what this tool is or what it duplicates.

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

Usage Guidelines5/5

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

It names the exact alternative and instructs 'call that instead', which is the strongest possible when-to-use guidance: an agent should never select this tool for new work. The validity window (until 2027-01-12) bounds the only case where use is acceptable.

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