Discovery
Run Saved Workflow
run_workflowBenchmark and above
Resolve a saved workflow by id and return a structured execution plan for a single ticker. Each plan entry names a real MCP tool or SOP plus its ticker-substituted arguments; the calling agent invokes them in order, applying any `skip_if` predicate against the previous step's ...
Example Call
example_call.pypython
# Using the Valuein MCP server from Python (via MCP SDK)# Or call directly from Claude / Cursor after setup result = await client.call_tool( "run_workflow", arguments={ "workflow_id": "EXAMPLE"})print(result)Direct tool call:run_workflow(...)
Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
workflow_id | string | required | Workflow id returned by the frontend workflow builder. |
ticker | string | optional | US-listed ticker the workflow should run against, e.g. 'AAPL'. Pass either `ticker` (single) or `tickers` (batch up to 50). Exactly one is required. |
tickers | array | optional | Batch mode — array of US-listed tickers, up to 50. When provided, the response has `plans[]` (one plan per ticker) instead of `plan`. Parity with the frontend batch-runner so agents can request 'plan over my watchlist' in a single call. |
Output Fields
metaworkflowtickerplanplansinstructionsExample Response
Illustrative
response.jsonjson
{ "meta": null, "workflow": null, "ticker": "AAPL", "plan": "sp500", "plans": null, "instructions": null}Shape only — field names match the live schema; values are placeholders, not real filings. See MCP server for the structured response shape.
Notes
Available from the Benchmark plan and above.
Plan Access
Sample (guest)
Not includedBenchmark (token)
AvailablePro
AvailableInstitutional
AvailableRelated Tools
Index names are trademarks of their owners; Valuein is not affiliated with or endorsed by any index provider.