Skip to main content
Glama
INo-xious

stockbit-mcp

by INo-xious

stream

Read-only

Retrieve Stockbit community posts filtered by ticker, keyword, category, or date to monitor Indonesian market sentiment and discover trading ideas, news, reports, and insider posts.

Instructions

Posts from Stockbit's social stream: news, trading ideas, filed reports, insider posts, charts, polls and predictions. With no symbol this is the market-wide stream; with a symbol it is that company's stream, which is the same feed the Stockbit symbol page shows. This is community- and media-written Indonesian text, not market data. Use it for sentiment and as a pointer to a source; never quote a price, a ratio or an earnings figure from a post. category selects the tab and is sent verbatim: STREAM_CATEGORY_NEWS is the News tab, _REPORTS the filed-research tab, _INSIDER insider posts. STREAM_CATEGORY_LIKED and _SAVED are the signed-in account's own, not the market's, and the three *_WATCHLIST values scope the feed to the user's lists — watchlist_ids narrows that to named lists (ids come from the watchlist tools; they are numeric). report_type only narrows STREAM_CATEGORY_REPORTS. It is sent as given for any other category and Stockbit is free to ignore it there. from_date/to_date are YYYY-MM-DD and are calendar-checked before the request goes out, so a typo (2026-02-30, 20260803) fails loudly instead of quietly returning today. Either end may stand alone; an inverted pair is rejected. Paging is a CURSOR, not an offset: there is no page number or offset. Take nextCursor from the result and send it as last_stream_id to get the rows AFTER the ones you have seen; calling again without it returns the same rows. nextCursor is null when the page is empty or its last row carried no id, which means the walk cannot be continued rather than that it has ended. An empty items with a non-null source is a genuine zero — a quiet symbol or a narrow keyword — and not a reason to retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows. Omitted = Stockbit's own page size (30 on the route observed).
symbolNoIDX ticker, e.g. BBRI. Omit for the market-wide stream.
keywordNoFull-text search over post content.
to_dateNoYYYY-MM-DD, inclusive
categoryNoWire spelling, case-sensitive. Omitted = Stockbit's default feed.
from_dateNoYYYY-MM-DD, inclusive
last_replyNoSecond cursor Stockbit's client sends beside last_stream_id; its role is unverified, so leave it unset.
report_typeNoNarrows STREAM_CATEGORY_REPORTS only.
watchlist_idsNoNumeric watchlist ids, for the *_WATCHLIST categories.
last_stream_idNoCursor: the `nextCursor` from the previous page.
Behavior5/5

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

Annotations already mark this read-only and non-destructive, and the description goes far beyond them: category is sent verbatim, report_type is ignored for non-report categories, date validation fails loudly, the cursor has specific semantics with nextCursor null meaning the walk cannot continue, and empty items with non-null source is a genuine zero not a retry trigger. This is exceptional behavioral disclosure.

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 long but densely informative; every sentence covers a distinct behavior or constraint. It is well-organized by topic: content type, category semantics, report_type behavior, date handling, and paging. The most important caveat (not market data) is front-loaded.

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?

This is a high-complexity 10-parameter tool with no output schema, so the description carries the full burden for response semantics. It extensively explains paging, cursor behavior, empty results, and the meaning of nextCursor. Given the complexity, nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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, but the description adds substantial meaning: it maps category enum values to UI tabs, explains watchlist_ids come from watchlist tools and are numeric, states date format and validation failure behavior, and documents the cursor relationship between last_stream_id and nextCursor. This far exceeds what the schema alone provides.

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 states a specific verb and resource: it posts from Stockbit's social stream with concrete content examples (news, trading ideas, reports, charts, polls, predictions). It clearly distinguishes this from market data tools by warning it is community/media-written text, not market data. The symbol/no-symbol distinction further clarifies the two main modes exactly.

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?

The description gives explicit usage guidance: use for sentiment and source pointers, never for quoting prices/ratios/earnings. It explains when to omit vs provide a symbol, how category selects tabs, and how report_type applies only to reports. This is actionable enough for an agent to choose and invoke it correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/INo-xious/stockbit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server