Skip to main content
Glama

Run Stream Now

run_stream_now

[Acquire · stream price/page] Trigger an immediate run of an active stream, bypassing its schedule. The run is fire-and-forget — the response confirms the dispatch but post collection happens asynchronously. Credits are charged for pages actually walked, not pages requested: one page is taken upfront and the rest settled when the run finishes, so a run that stops early (or fails) costs less than max_pages implies. Paused streams must be resumed first. Use list_streams or get_stream_feed to see results once the run completes.

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": {
      "stream_id": "<stream_id>"
    },
    "name": "run_stream_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeNoContinue a person_interests backfill from where the deepest previous run stopped, instead of re-walking the newest pages. Use this for 'pull more history' — without it you re-fetch and re-pay for content you already have. No effect on a stream that has never been walked.
max_pagesNoUpper bound on pages for this run (1-5, default 1) — a budget, not a price. Honoured for external_profile, company and person_interests. You are billed only for pages actually walked; a person_interests stream stops as soon as it reaches engagement it already has, so a deep budget usually costs one page. A page is ~50 posts for profile/company feeds and ~100 engagement events for person_interests, where one page means one reactions call plus one comments call. Other stream types ignore this — their sources aren't paginated.
stream_idYesStream ID from list_streams
history_daysNoHow far back this run should reach, in days. Bounds the walk by TIME where max_pages bounds it by COST — it stops at whichever limit it hits first, so pair a deep window with enough pages to reach it. Honoured for external_profile, company and person_interests; the search types ignore it. Applies to this run alone; it is never saved on the stream. Combines with resume: 'go further back, but only as far as this'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false) by disclosing the asynchronous fire-and-forget execution model and the response's limited meaning. The billing mechanics — one page charged upfront, remainder settled on completion, early stop or failure costs less than max_pages implies — are exactly the kind of side-effect detail an agent needs before spending credits.

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?

Front-loaded with the action, then the execution model, then billing, then the precondition — a sensible order with no filler sentences. It is dense but slightly long, and the billing explanation partly restates the max_pages schema description.

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?

With no output schema, the description carries the return-value burden and does so: the response only confirms dispatch, with collection happening asynchronously and results read via list_streams or get_stream_feed. Combined with the credit model and the paused-stream prerequisite, an agent has everything needed to invoke and interpret this tool correctly.

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 schema already documents all four parameters, making 3 the baseline. The description still adds value by explaining that the credit settlement makes max_pages a budget rather than a price and by reinforcing resume/history_days semantics, though the per-parameter detail largely mirrors the schema text rather than extending it.

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 ('Trigger an immediate run of an active stream') and immediately scopes it with 'bypassing its schedule', which distinguishes it from any scheduled-run behavior. The bracketed tag '[Acquire · stream price/page]' plus the explicit contrast with list_streams/get_stream_feed makes the tool's role unmistakable.

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?

Gives an explicit precondition ('Paused streams must be resumed first'), which routes the agent to resume_stream before calling, and names the follow-up tools (list_streams, get_stream_feed) for retrieving results. It also implicitly rules out use when a scheduled run is sufficient by framing the tool as a schedule bypass.

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.

Resources