ib-gateway-mcp

Historical headlines

get_historical_news

Read-only

Fetch past news headlines for an instrument, newest first. Get provider codes and article IDs for each headline, with publication timestamps, to retrieve full articles.

Instructions

Return past news headlines about one instrument, newest first.

Each headline has provider_code and article_id for get_news_article, plus the
publication time (UTC). Works for stocks and other instruments IBKR tags news
with. Default limit 50, at most 300 (IBKR's cap per request); for more, move `end`
back to the oldest time returned. Needs a subscription to each provider searched
(see get_news_providers).
Errors: invalid_request for a provider the login is not subscribed to; not_found
when there are no headlines in the range (widen it); request_timeout when IBKR
does not answer within 4 seconds (retry with a narrower range).

Input Schema

TableJSON Schema

Name	Required	Description
`end`	No	End of the range, ISO 8601 (no time zone means UTC). Omit for now.
`limit`	No	Maximum number of items to return. Omit for the tool's default; larger values are capped. The result's truncated flag says whether more were available.
`start`	No	Start of the range, ISO 8601 (no time zone means UTC). Omit for none.
`contract`	Yes	The instrument. A con_id alone is unambiguous; otherwise give symbol and sec_type, plus expiry, strike and right for options.
`provider_codes`	No	Provider codes to search, e.g. ["BRFG", "DJNL"] (from get_news_providers). Omit for every subscribed provider.

Output Schema

TableJSON Schema

Name	Required	Description
`end`	No	End of the range asked for (UTC).
`start`	No	Start of the range asked for (UTC).
`contract`	Yes
`headlines`	Yes
`truncated`	No	True when the result was cut to the limit.
`provider_codes`	Yes	The providers that were searched.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint annotation by disclosing pagination behavior (default 50, max 300, move end back), subscription requirements, supported instrument types, UTC timestamps, and specific error conditions with recovery guidance. This is rich, actionable behavioral context.

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?

The description is dense but every sentence earns its place: purpose, return fields, supported instruments, limits, pagination, subscriptions, and errors. It is front-loaded with the core purpose and then systematically covers invocation-relevant details.

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?

Given the 5-parameter schema, output schema, and read-only annotations, the description covers everything an agent needs to invoke this correctly: what is returned, how to paginate, provider requirements, and expected errors. Nothing important is missing.

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. The description adds value beyond the schema by specifying the exact default limit (50), the cap (300), the pagination technique using end, and the subscription-per-provider constraint.

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?

The description opens with a specific verb and resource: 'Return past news headlines about one instrument, newest first.' It clearly distinguishes the tool from siblings like get_news_article and get_news_providers by explaining that headlines carry provider_code and article_id for use with get_news_article.

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 practical workflow context: headlines reference get_news_article, provider codes come from get_news_providers, and subscription requirements are stated. It stops short of explicitly saying 'use this for historical news, not live news' or naming subscribe_news as the alternative, so it misses the top score.

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

Deploy Server